| 3 |
Approval of the Agenda |
|
| R3-251501 |
RAN3#127-bis Meeting Agenda |
RAN3 Chair |
| 4 |
Approval of the minutes from previous meetings |
|
| R3-251502 |
RAN3#127 Meeting Report |
ETSI-MCC |
| 5 |
Documents for immediate consideration |
|
| R3-251503 |
Guidelines for RAN3 Meetings |
RAN3 Chair, RAN3 Vice-Chairs |
| 7 |
General, protocol principles and issues |
|
| R3-251504 |
TR 30.531 v1.57.0 Work Plan and Working Procedures - RAN WG3 |
ETSI-MCC |
| R3-251626 |
State of the art and perspectives on methods and tools for managing CRs and TSs in 3GPP |
Ericsson |
| R3-252247 |
6G specification format modernization: towards Automation-Native |
Nokia |
| 8.1 |
New Incoming LSs |
|
| R3-251505 |
LS on stage 1 requirements for the support for PWS over satellite NGRAN in Rel-17 |
CT1(Qualcomm) |
| R3-251506 |
LS on PWS enhancements for MWAB and MBSR |
CT1(Ericsson) |
| R3-251511 |
LS on Rel-19 higher layers parameters list Post RAN1#120 |
RAN1(Ericsson) |
| R3-251518 |
Geofencing in ETWS for NR and NB-IoT NTN |
RAN2(Ericsson) |
| R3-251519 |
LS to CT1 and CT4 on maximum warning message size |
RAN2(Google) |
| R3-251520 |
LS on Signalling for 7 MHz Channel Bandwidth |
RAN4(T-mobile) |
| R3-251521 |
Reply LS on emergency call back and paging |
SA2(ZTE) |
| R3-251522 |
Reply LS on Satellite IDs for store-and-forward operation |
SA2(CATT) |
| R3-251527 |
Reply to RAN2 LS on Number of UEs in RRC_INACTIVE state with data transmission |
SA5(China Telecom) |
| R3-251530 |
LS on Vendor Specific Trace Record |
SA5(Ericsson) |
| R3-251654 |
Enhancement of Trace for support of vendor specific trace records [TraceQoE_OAM] |
Nokia |
| R3-251655 |
Enhancement of Trace for support of vendor specific trace records [TraceQoE_OAM] |
Nokia |
| R3-251656 |
Enhancement of Trace for support of vendor specific trace records [TraceQoE_OAM] |
Nokia |
| R3-251657 |
Enhancement of Trace for support of vendor specific trace records [TraceQoE_OAM] |
Nokia |
| R3-251658 |
Enhancement of Trace for support of vendor specific trace records [TraceQoE_OAM] |
Nokia |
| R3-251659 |
Enhancement of Trace for support of vendor specific trace records [TraceQoE_OAM] |
Nokia |
| R3-251666 |
Emergency Callback and Paging |
Nokia |
| R3-251667 |
Response LS on Emergency Callback and Paging |
Nokia |
| R3-251668 |
Correction of Emergency Calback and eDRX |
Nokia |
| R3-251669 |
Correction of Emergency Calback and eDRX |
Nokia |
| R3-251883 |
Further discussion on emergency services and eDRX |
ZTE Corporation |
| R3-251884 |
[Draft] Reply LS on emergency call back and paging |
ZTE Corporation |
| R3-251885 |
Clarification on emergency services and eDRX |
ZTE Corporation |
| R3-251886 |
Clarification on emergency services and eDRX |
ZTE Corporation |
| R3-251896 |
Discussion on the emergency services and eDRX |
Huawei |
| R3-251897 |
emergency services and eDRX for RRC inactive UE |
Huawei |
| R3-251898 |
emergency services and eDRX for RRC inactive UE |
Huawei |
| R3-251899 |
[Draft] Reply LS on emergency call back and paging |
Huawei |
| R3-252003 |
Discussion on the support for PWS over satellite NGRAN in Rel-17 and beyond |
Huawei |
| R3-252004 |
Remove the PWS support for IoT NTN |
Huawei |
| R3-252005 |
Remove the PWS support for IoT NTN |
Huawei |
| R3-252006 |
Remove the PWS support for NR NTN |
Huawei |
| R3-252007 |
Remove the PWS support for NR NTN |
Huawei |
| R3-252008 |
[DRAFT] Reply LS on stage 1 requirements for the support for PWS over satellite NGRAN in Rel-17 |
Huawei |
| R3-252020 |
Discussion on SA2 LS regarding Emergency PDU Session |
Ericsson |
| R3-252021 |
[Draft] Reply LS on emergency call back and paging |
Ericsson |
| R3-252095 |
Discussion on 7MHz channel bandwidth |
Nokia |
| R3-252096 |
TP (BL CR TS38.473) Support for 7MHz transmission bandwidth |
Nokia |
| R3-252097 |
TP (BL CR TS38.423) Support for 7MHz transmission bandwidth |
Nokia |
| R3-252098 |
[Draft] Reply LS on Signalling for 7 MHz Channel Bandwidth |
Nokia |
| R3-252194 |
Discussion on Vendor Specific Trace Record |
ZTE Corporation |
| R3-252195 |
Vendor Specific Trace Record_38413 |
ZTE Corporation |
| R3-252196 |
Vendor Specific Trace Record_38423 |
ZTE Corporation |
| R3-252197 |
Vendor Specific Trace Record_38473 |
ZTE Corporation |
| R3-252198 |
Vendor Specific Trace Record_37483 |
ZTE Corporation |
| R3-252199 |
Vendor Specific Trace Record_36413 |
ZTE Corporation |
| R3-252200 |
Vendor Specific Trace Record_36423 |
ZTE Corporation |
| R3-252201 |
Reply LS on Vendor Specific Trace Record |
ZTE Corporation |
| R3-252217 |
Discussion on the Vendor Specific Trace Record |
Huawei |
| R3-252218 |
[Draft] Reply LS on the Vendor Specific Trace Record |
Huawei |
| R3-252219 |
Correction to Trace Depth on Vendor Specific Trace Record |
Huawei |
| R3-252220 |
Correction to Trace Depth on Vendor Specific Trace Record |
Huawei |
| R3-252221 |
Correction to Trace Depth on Vendor Specific Trace Record |
Huawei |
| R3-252222 |
Correction to Trace Depth on Vendor Specific Trace Record |
Huawei |
| R3-252238 |
Clarification on emergency services and eDRX over NG |
ZTE Corporation |
| R3-252239 |
Clarification on emergency services and eDRX over NG |
ZTE Corporation |
| R3-252254 |
Trace Depth for Vendor Specific Trace Record [Vendor_Specific_Trace] |
Ericsson |
| R3-252255 |
Trace Depth for Vendor Specific Trace Record [Vendor_Specific_Trace] |
Ericsson |
| R3-252256 |
Trace Depth for Vendor Specific Trace Record [Vendor_Specific_Trace] |
Ericsson |
| R3-252257 |
Trace Depth for Vendor Specific Trace Record [Vendor_Specific_Trace] |
Ericsson |
| R3-252258 |
Trace Depth for Vendor Specific Trace Record [Vendor_Specific_Trace] |
Ericsson |
| R3-252259 |
Trace Depth for Vendor Specific Trace Record [Vendor_Specific_Trace] |
Ericsson |
| R3-252260 |
[Draft] Reply LS on Vendor Specific Trace Record |
Ericsson |
| R3-252262 |
Response to R3-252095 |
ZTE Corporation |
| R3-252263 |
Response to R3-252003 |
ZTE Corporation |
| R3-252266 |
Correction of Emergency Calback and eDRX |
Nokia |
| R3-252267 |
Correction of Emergency Calback and eDRX |
Nokia |
| R3-252273 |
Reply LS on emergency call back and paging |
RAN3(ZTE) |
| R3-252308 |
Reply LS on Vendor Specific Trace Record |
RAN3(Ericsson) |
| R3-252393 |
Trace Depth for Vendor Specific Trace Record |
Nokia, Ericsson, Huawei, ZTE Corporation |
| R3-252394 |
Trace Depth for Vendor Specific Trace Record |
Ericsson, Huawei, ZTE Corporation, Nokia |
| R3-252395 |
Trace Depth for Vendor Specific Trace Record |
Huawei, Ericsson, Nokia, ZTE Corporation |
| R3-252396 |
Trace Depth for Vendor Specific Trace Record |
ZTE Corporation, Ericsson, Nokia, Huawei |
| R3-252400 |
Correction of Emergency Call and eDRX |
Nokia, ZTE, Huawei, Ericsson, Qualcomm Incorporated |
| R3-252401 |
Correction of Emergency Call and eDRX |
Nokia, ZTE, Huawei, Ericsson, Qualcomm Incorporated |
| R3-252402 |
Reply LS on emergency call back and paging |
RAN3(ZTE) |
| R3-252403 |
Trace Depth for Vendor Specific Trace Record |
Huawei, Ericsson, ZTE Corporation, Nokia |
| 8.3 |
Left over LSs / pending actions |
|
| R3-251635 |
Discussion on energy saving indication from CN to RAN |
CATT |
| R3-251636 |
(draft) Reply LS on energy saving indication from CN to RAN |
CATT |
| R3-251653 |
On Energy saving indicator from AMF |
Nokia |
| R3-251802 |
Discussion on energy saving indication from CN to RAN |
Huawei, CATT, NEC |
| R3-251803 |
[draft] Reply LS on energy saving indication from CN to RAN |
Huawei, CATT, NEC |
| R3-251840 |
Discussion on energy saving indicator from CN to RAN |
Samsung |
| R3-251841 |
[draft] Reply LS on energy saving indication from CN to RAN |
Samsung |
| R3-251887 |
Discussion on energy saving indication from CN to RAN |
ZTE Corporation |
| R3-251888 |
[DRAFT] Reply LS on energy saving indication from CN to RAN |
ZTE Corporation |
| R3-252011 |
Further discussion on Energy Saving Indicator |
Ericsson, Jio Platforms (JPL), BT |
| R3-252015 |
[Draft] Reply LS on energy saving indicator from CN to RAN |
Ericsson, Jio Platforms (JPL), BT |
| R3-252322 |
[draft] Reply LS on energy saving indication from CN to RAN |
Huawei, CATT, NEC |
| R3-252404 |
Reply LS on energy saving indication from CN to RAN |
RAN3(Huawei) |
| 9.2 |
NR |
|
| R3-251512 |
Reply LS on Update of Broadcast MCCH Information |
RAN2(Nokia) |
| R3-251516 |
Reply LS on QMC Coordination for RRC Segmentation in NR-DC |
RAN2(ZTE) |
| R3-251532 |
Reply LS on L3 measurement based LTM support over F1 |
RAN(Vodafone) |
| R3-251598 |
Consideration on (S-)CPAC cancel and SN Release |
Huawei, Lenovo, LG Electronics, Google, China Telecom |
| R3-251599 |
Correction of CPC Cancel and SN Release |
Huawei, Lenovo, LG Electronics, Google, ZTE, China Telecom |
| R3-251600 |
Correction of CPC Cancel and SN Release |
Huawei, Lenovo, LG Electronics, Google, Nokia, Ericsson, ZTE, China Telecom |
| R3-251601 |
Correction of Conditional PSCell Change Cancel for S-CPAC |
Huawei, Lenovo, LG Electronics, Google, Nokia, Ericsson, ZTE, China Telecom |
| R3-251602 |
Correction of RRC Establishment Cause for CIoT |
Huawei, Nokia, ZTE, Qualcomm Incorporated |
| R3-251634 |
Discussion on L3 measurement report for SCell activation |
CATT, China Telecom, CMCC |
| R3-251691 |
CR in TS 38.423 for Rel-18 single-hop U2N relay |
NEC |
| R3-251704 |
Miscellaneous corrections for non-3GPP access |
ZTE Corporation, Nokia, Nokia Shanghai Bell, Samsung |
| R3-251705 |
Corrections for multi-path relay |
ZTE Corporation, China Telecom, Nokia, Nokia Shanghai Bell, Samsung, CATT |
| R3-251708 |
Correction to CPAC MCG configuration cancellation |
Google |
| R3-251709 |
Correction to CPAC MCG configuration cancellation |
Google |
| R3-251710 |
Clarification on handover for multicast MRB |
Google |
| R3-251711 |
Clarification on handover for multicast MRB |
Google |
| R3-251746 |
Discussion on Update of Broadcast MCCH Information |
Huawei, CBN, CMCC, Qualcomm Incorporated, Ericsson, ZTE |
| R3-251747 |
Correction on PDCP packets discard in case of MBS broadcast path update |
Huawei, CBN, CMCC, Qualcomm Incorporated, Ericsson, ZTE, Nokia |
| R3-251761 |
(TP to TS 38.473) Unified solution to support L3 measurement based R18 LTM |
Qualcomm Inc, Apple Inc, AT&T, Boost Mobile Networks (Dish),JIO Platforms, Rakuten, Vivo, Tejas Networks, Xiaomi |
| R3-251771 |
Correction on UAV Cell Information over X2 interface |
ZTE Corporation, China Telecom, China Unicom |
| R3-251773 |
Correction on Alternative QoS parameter |
CATT, Nokia, Qualcomm |
| R3-251790 |
Correction on Bearer Context NG-U TNL Information for an MBS Session |
ZTE Corporation, Ericsson, Huawei, CATT, Lenovo, Nokia |
| R3-251804 |
Correction of Old AMF and Backup AMF Name |
Huawei, China Unicom, China Telecom, Vodafone |
| R3-251805 |
Correction of Old AMF and Backup AMF Name |
Huawei, China Unicom, China Telecom, Vodafone |
| R3-251806 |
Correction of Old AMF and Backup AMF Name |
Huawei, China Unicom, China Telecom, Vodafone |
| R3-251808 |
Discussion on SRS information |
Samsung, ZTE, Huawei, Ericsson, Nokia, China Telecom, Qualcomm, CMCC, CATT |
| R3-251809 |
Discussion on QMC coordination for RRC segmentation in NR-DC |
Samsung, Nokia, ZTE, China Unicom, China Telecom, Lenovo |
| R3-251810 |
Correction to QMC coordination for RRC segmentation in NR-DC |
Samsung, Nokia, ZTE, China Unicom, China Telecom, Lenovo |
| R3-251816 |
Clarification for propagation of MDT Configuration in stage 2 |
ZTE Corporation |
| R3-251820 |
Correction of TSC Traffic Characteristics |
Huawei, Nokia, China Telecom, Ericsson |
| R3-251821 |
Correction of TSC Traffic Characteristics |
Huawei, Nokia, China Telecom, Ericsson |
| R3-251839 |
Stage 2 updates for support of L3 measurements based LTM(option1&option5) |
CATT, Ericsson, Vodafone, ZTE, Google, Samsung, LG Electronics, NTT DoCoMo, Nokia |
| R3-251874 |
F1 support for L3 measurements-based LTM |
ZTE Corporation, Ericsson, CATT, Vodafone, Nokia, LG Electronics, Samsung |
| R3-251875 |
Correction on S-CPAC |
ZTE Corporation, China Telecom, CATT, Huawei, Lenovo |
| R3-251876 |
Discussion on support of Carrier Bandwidth less than 5MHz |
ZTE, China Telecom, CATT, China Unicom |
| R3-251877 |
Clarification on Carrier Bandwidth less than 5MHz in TS38.423 |
ZTE Corporation, China Telecom, CATT, China Unicom, Huawei, Qualcom, Lenovo, LG Electronics |
| R3-251878 |
Clarification on Carrier Bandwidth less than 5MHz in TS38.473 |
ZTE Corporation, China Telecom, CATT, China Unicom, Huawei, Qualcom, Lenovo, LG Electronics |
| R3-251879 |
Clarification on Carrier Bandwidth less than 5MHz in TS36.423 |
ZTE Corporation, China Telecom, CATT, China Unicom |
| R3-251880 |
Clarification on data transmission for EDT |
ZTE Corporation, China Telecom, Huawei |
| R3-251906 |
On the special case of Nrb 12 and Nrb 20 Transmission Bandwidth configurations |
Ericsson, UIC, Qualcomm |
| R3-251907 |
Additional abnormal conditions for data collection parameters |
Ericsson, ZTE Corporation, Jio Platforms, InterDigital |
| R3-251908 |
Additional procedural text for data collection configuration |
Ericsson, ZTE Corporation, Jio Platforms, InterDigital |
| R3-251956 |
Option 5b for F1 support for L3 measurements-based LTM |
Samsung, Nokia, Ericsson, ZTE, LG Electronics, CATT, Verizon |
| R3-251958 |
Discussion on Security Issue for State Transition from RRC_INACTIVE to RRC_CONNECTED |
China Telecom, Huawei, CATT, ZTE |
| R3-251959 |
Correction on Security Configuration in Bearer Context Setup Message |
China Telecom, ZTE, Huawei, CATT, Lenovo |
| R3-251966 |
Correction on Security Configuration in Bearer Context Setup Message |
China Telecom, ZTE, Huawei, CATT, Lenovo |
| R3-251967 |
Correction on Security Configuration in Bearer Context Setup Message |
China Telecom, ZTE, Huawei, CATT, Lenovo |
| R3-251968 |
Correction on Security Configuration in Bearer Context Setup Message |
China Telecom, ZTE, Huawei, CATT, Lenovo |
| R3-251969 |
Discussion on Cell Information for ATG and UAV |
China Telecom |
| R3-251970 |
Correction on ATG Information over Xn interface |
China Telecom, CATT, China Unicom |
| R3-251973 |
Correction on UAV Information over F1 interface |
China Telecom, ZTE, CATT, China Unicom |
| R3-251974 |
Correction on UAV Information over Xn interface |
China Telecom, ZTE, CATT, China Unicom |
| R3-251984 |
On packet loss metric in UE performance |
Ericsson, JIO Platforms, InterDigital |
| R3-251985 |
Correction to exclude Packet Loss as a UE Performance metric |
Ericsson, JIO Platforms, InterDigital |
| R3-251987 |
Stage 3 corrections for AI/ML for NG-RAN - Solution A |
Huawei, Nokia, Deutsche Telekom, Jio Platforms, FiberCop, Qualcomm, BT |
| R3-251988 |
Stage 3 corrections for AI/ML for NG-RAN - Solution B |
Huawei, Nokia, Deutsche Telekom, Jio Platforms, FiberCop, Qualcomm, BT |
| R3-252014 |
Correction of MBS Distribution Setup |
Nokia, CATT, Qualcomm Incorporated, Huawei, Ericsson, Orange, ZTE |
| R3-252016 |
Correction of MBS Distribution Setup |
Nokia, CATT, Qualcomm Incorporated, Huawei, Ericsson, Orange, ZTE |
| R3-252017 |
Correction of MBS Distribution Setup |
Nokia, CATT, Qualcomm Incorporated, Huawei, Ericsson, Orange, ZTE |
| R3-252022 |
[DRAFT] LS on Handling of UE Radio Capability for Paging |
Ericsson, CMCC, Huawei, CATT, Qualcomm Inc., Vodafone, ZTE, Nokia |
| R3-252060 |
F1 support for L3 measurements-based LTM |
Ericsson, CATT, ZTE, Lenovo, LG Electronics, Google, Verizon Wireless |
| R3-252061 |
Option 1 for F1 support of L3 measurements-based LTM |
Ericsson, Vodafone, CATT, ZTE, NTT DoCoMo, Verizon Wireless, Nokia, Samsung, LG Electronics, Lenovo, Google |
| R3-252062 |
Option 5 for F1 support of L3 measurements-based LTM |
Ericsson, Vodafone, CATT, ZTE, NTT DoCoMo, Verizon Wireless, Nokia, Samsung, LG Electronics, Lenovo, Google |
| R3-252063 |
Correction on the UE Initial Access procedure |
Ericsson |
| R3-252064 |
Correction on the UE Initial Access procedure |
Ericsson |
| R3-252065 |
Correction on the UE Initial Access procedure |
Ericsson |
| R3-252066 |
Correction to exclude Packet Loss as a UE Performance metric |
Ericsson, JIO Platforms, InterDigital |
| R3-252067 |
Additional procedural text for data collection configuration |
Ericsson, ZTE Corporation, Jio Platforms, InterDigital |
| R3-252068 |
Correction on the UE Initial Access procedure |
Ericsson |
| R3-252069 |
Update of Broadcast MCCH Information for MBS packets discard and multiple Cell-ID case |
Nokia |
| R3-252070 |
Response LS on Update of Broadcast MCCH Information |
Nokia |
| R3-252075 |
Discussion on Optional IEs in the Data Collection Reporting Initiation procedure |
Nokia, Huawei, Deutsche Telekom, Jio Platforms, FiberCop, Qualcomm, BT |
| R3-252076 |
Stage 3 corrections for AI/ML for NG-RAN |
Nokia, Huawei, Deutsche Telekom, Jio Platforms, FiberCop, Qualcomm, BT |
| R3-252112 |
Correction of Paging Priority Indicator (PPI) |
Huawei, China Unicom, China Telecom, NEC |
| R3-252113 |
Correction of Paging Priority Indicator (PPI) |
Huawei, China Unicom, China Telecom, NEC |
| R3-252114 |
Correction of Paging Priority Indicator (PPI) |
Huawei, China Unicom, China Telecom, NEC |
| R3-252115 |
Correction of Paging Priority Indicator (PPI) |
Huawei, China Unicom, China Telecom, NEC |
| R3-252126 |
Further discussion on L3 measurement based LTM |
Huawei, China Telecom, CMCC |
| R3-252127 |
Support of L3 measurement based LTM over F1 |
Huawei, China Telecom, CMCC |
| R3-252128 |
Support of L3 measurement based LTM over F1 |
Huawei, China Telecom, CMCC |
| R3-252129 |
Support of L3 measurement based LTM over F1 |
Huawei, China Telecom, CMCC |
| R3-252130 |
Correction on Served Cells To Update |
Huawei, CMCC, China Unicom |
| R3-252131 |
Correction on Served Cells To Update |
Huawei, CMCC, China Unicom |
| R3-252132 |
Correction on Served Cells To Update |
Huawei, CMCC, China Unicom |
| R3-252133 |
Correction on Served Cells To Update |
Huawei, CMCC, China Unicom |
| R3-252136 |
Discussion on the PDCP SN gap report handling during UE’s handover |
Huawei, CATT, Xiaomi, China Telecom, LG Electronics |
| R3-252137 |
Correction for MDBV in alternative QoS |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CMCC |
| R3-252138 |
Correction for MDBV in alternative QoS |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CMCC |
| R3-252139 |
Correction for MDBV in alternative QoS |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CMCC |
| R3-252140 |
Correction for MDBV in alternative QoS |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CMCC |
| R3-252141 |
Correction on the mobile IAB procedures |
Huawei, Lenovo, ZTE, Nokia, Nokia Shanghai Bell |
| R3-252146 |
Discussion on L3 measurement based LTM |
NTT DOCOMO INC.. |
| R3-252149 |
Stage-2 Support of L3 measurement based LTM for DU based solution |
Qualcomm Inc, AT&T, Apple Inc, JIO Platforms, Boost Mobile Networks (Dish), Rakuten, Tejas Networks, Vivo, Xiaomi |
| R3-252150 |
Support of L3 measurement based LTM over F1 for DU based solution |
Qualcomm Inc, AT&T, Apple Inc, JIO Platforms, Boost Mobile Networks (Dish), Rakuten, Tejas Networks, Vivo, Xiaomi |
| R3-252151 |
Support of L3 measurement based LTM over F1 for DU based solution (stage-3) |
Qualcomm Inc, AT&T, Apple Inc, JIO Platforms, Boost Mobile Networks (Dish), Rakuten, Tejas Networks, Vivo, Xiaomi |
| R3-252158 |
Introduction to coordination for QoE RRC segmentation in NR-DC |
ZTE Corporation,Samsung, China Unicom, China Telecom, Lenovo |
| R3-252159 |
[Draft] Reply LS on QMC Coordination for RRC Segmentation in NR-DC |
ZTE Corporation |
| R3-252166 |
Option 5b for F1 support for L3 measurements-based LTM |
Samsung, Nokia, Ericsson, ZTE, LG Electronics, CATT, Verizon Wireless |
| R3-252188 |
Correction on UE radio capability for paging information |
CMCC, Ericsson, Huawei, CATT, Qualcomm Inc., Vodafone, ZTE, Nokia |
| R3-252189 |
Correction on UE radio capability for paging information |
CMCC, Ericsson, Huawei, CATT, Qualcomm Inc., Vodafone, ZTE, Nokia |
| R3-252190 |
Correction on UE radio capability for paging information |
CMCC, Ericsson, Huawei, CATT, Qualcomm Inc., Vodafone, ZTE, Nokia |
| R3-252216 |
Further discussions on QMC Coordination for RRC Segmentation in NR-DC |
Huawei |
| R3-252232 |
Additional procedural text measured UE trajectory request |
ZTE Corporation, Ericsson, InterDigital, Jio Platforms (JPL) |
| R3-252233 |
Additional abnormal conditions for measured UE trajectory request |
ZTE Corporation, Ericsson, InterDigital, Jio Platforms (JPL) |
| R3-252234 |
Correction on maximum number of failed measurement objects |
ZTE Corporation, Samsung, CMCC, China Telecom, China Unicom |
| R3-252235 |
Correction on the NRPPa positioning procedure |
ZTE Corporation, Nokia, Ericsson, Huawei, CATT, CMCC, Samsung |
| R3-252253 |
(TP to TS 38.473) Unified solution to support L3 measurement based R18 LTM |
Qualcomm Inc, Apple Inc, AT&T, Boost Mobile Networks (Dish),JIO Platforms, Fujitsu, Rakuten, Vivo, Tejas Networks, Xiaomi |
| R3-252264 |
Discussion on support of Carrier Bandwidth less than 5MHz |
ZTE, China Telecom, CATT, China Unicom |
| R3-252265 |
CB:#4_L3MeasurementsLTM |
Vodafone |
| R3-252268 |
Correction of MBS Distribution Setup |
Nokia, CATT, Qualcomm Incorporated, Huawei, Ericsson, Orange, ZTE |
| R3-252269 |
Correction of MBS Distribution Setup |
Nokia, CATT, Qualcomm Incorporated, Huawei, Ericsson, Orange, ZTE |
| R3-252270 |
Correction on Bearer Context NG-U TNL Information for an MBS Session |
ZTE Corporation, Ericsson, Huawei, CATT, Lenovo, Nokia |
| R3-252271 |
CB:#5_QMCCordination |
Samsung |
| R3-252272 |
Correction of CPC Cancel and SN Release |
Huawei, Lenovo, LG Electronics, Google, Nokia, Ericsson, ZTE, China Telecom |
| R3-252274 |
CB:#7_R18AIML |
Ericsson |
| R3-252275 |
CB:#8_SRS |
Samsung |
| R3-252276 |
LS on Handling of UE Radio Capability for Paging |
RAN3(Ericsson) |
| R3-252277 |
CB:#10_Security |
China Telecom |
| R3-252285 |
Clarification on Carrier Bandwidth less than 5MHz |
ZTE Corporation, China Telecom, CATT, China Unicom, Huawei, Qualcomm, Lenovo, LG Electronics, Ericsson, Nokia |
| R3-252286 |
Clarification on Carrier Bandwidth less than 5MHz |
ZTE Corporation, China Telecom, CATT, China Unicom, Huawei, Qualcomm, Lenovo, LG Electronics, Ericsson, Nokia |
| R3-252309 |
Correction on S-CPAC |
ZTE Corporation, China Telecom, CATT, Huawei, Lenovo, Nokia, Ericsson, LG Electronics |
| R3-252313 |
Correction of RRC Establishment Cause for CIoT |
Huawei, Nokia, ZTE, Qualcomm Incorporated |
| R3-252314 |
Correction of TSC Traffic Characteristics |
Huawei, Nokia, China Telecom, Ericsson, ZTE |
| R3-252315 |
Correction of TSC Traffic Characteristics |
Huawei, Nokia, China Telecom, Ericsson, ZTE |
| R3-252316 |
Clarification on data transmission for EDT |
ZTE Corporation, China Telecom, Huawei, Nokia |
| R3-252317 |
Correction on Served Cells To Update |
Huawei, CMCC, China Unicom |
| R3-252318 |
Correction to CPAC MCG configuration cancellation |
Google |
| R3-252319 |
Correction to CPAC MCG configuration cancellation |
Google |
| R3-252324 |
Correction of Old AMF and Backup AMF Name |
Huawei, China Unicom, China Telecom, Vodafone, Nokia |
| R3-252339 |
Correction on the mobile IAB procedures |
Huawei, Lenovo, ZTE, Nokia, Nokia Shanghai Bell |
| R3-252359 |
Clarification on Security indication during State Transition from RRC_INACTIVE to RRC_CONNECTED |
China Telecom, Nokia, Huawei, Lenovo, ZTE, CATT |
| R3-252368 |
Option 5 for F1 support of L3 measurements-based LTM |
Ericsson, Vodafone, CATT, ZTE, NTT DoCoMo, Verizon Wireless, Nokia, Samsung, LG Electronics, Lenovo, Google, Huawei |
| R3-252390 |
Correction to exclude Packet Loss as a UE Performance metric |
Ericsson, JIO Platforms, InterDigital |
| R3-252391 |
Additional procedural text for data collection configuration |
Ericsson, ZTE Corporation, Jio Platforms, InterDigital |
| R3-252397 |
LS on Average Window for Alternative QoS |
RAN3(CATT) |
| R3-252399 |
Clarification on Security indication during State Transition from RRC_INACTIVE to RRC_CONNECTED |
China Telecom, Nokia, Huawei, LG Electronics, Lenovo, ZTE, CATT |
| R3-252406 |
Correction to CPAC MCG configuration cancellation |
Google, Nokia, ZTE Corporation, LG Electronics, Ericsson, Huawei |
| R3-252407 |
Correction to CPAC MCG configuration cancellation |
Google, Nokia, ZTE Corporation, LG Electronics, Ericsson, Huawei |
| R3-252412 |
Option 5 for F1 support of L3 measurements-based LTM |
Ericsson, Vodafone, CATT, ZTE, NTT DoCoMo, Verizon Wireless, Nokia, Samsung, LG Electronics, Lenovo, Google, Huawei |
| R3-252414 |
Additional procedural text measured UE trajectory request |
ZTE Corporation, Ericsson, InterDigital, Jio Platforms (JPL), CMCC |
| R3-252415 |
Additional procedural text for data collection configuration |
Ericsson, ZTE Corporation, Jio Platforms, InterDigital |
| R3-252417 |
Correction on the mobile IAB procedures |
Huawei, Lenovo, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| 10.1 |
General |
|
| R3-251535 |
(BL CR to 36.300 for SON) Addition of SON enhancements |
Lenovo |
| R3-251536 |
(BL CR to 38.413 for MDT) Addition of MDT enhancements |
Nokia |
| R3-251537 |
(BL CR to 38.423 for MDT) Addition of MDT enhancements |
CATT |
| R3-251538 |
(BL CR to 38.473 for SON) Addition of SON enhancements |
Huawei, Nokia, Jio |
| R3-251539 |
(BL CR to 38.401 for SON) Addition of SON enhancements |
ZTE Corporation, Nokia, Huawei, Lenovo, CATT, Ericsson, Samsung |
| R3-251540 |
(BL CR to 36.423) Addition of SON enhancements |
CATT, Samsung, Lenovo, Huawei, Ericsson, ZTE, CMCC, Nokia, Jio Platforms |
| R3-251541 |
(BL CR to 37.340 for SON) on MRO for S-CPAC |
CMCC |
| R3-251542 |
(BL CR to 38.300 for SON) Addition of SON enhancements |
China Unicom, ZTE Corporation, Samsung, Nokia, Lenovo |
| R3-251543 |
(BL CR to 38.423 for SON) Addition of SON enhancements |
ZTE Corporation, Samsung, Nokia, Lenovo, Jio |
| R3-252245 |
Workplan for Rel-19 SON_MDT Enhancement |
China Unicom, CMCC |
| R3-252360 |
(BL CR to 38.423 for SON) Addition of SON enhancements |
ZTE Corporation, Samsung, Nokia, Lenovo, Jio |
| R3-252512 |
(BL CR to 38.300 for SON) Addition of SON enhancements |
China Unicom, ZTE Corporation, Samsung, Nokia, Lenovo |
| R3-252513 |
(BL CR to 38.423 for SON) Addition of SON enhancements |
ZTE Corporation, Samsung, Nokia, Lenovo, Jio |
| 10.2 |
MRO Enhancements |
|
| R3-251514 |
LS on SON for LTM |
RAN2(Apple) |
| R3-251588 |
MRO enhancements for R18 mobility mechanisms |
Qualcomm Incorporated |
| R3-251593 |
(TP for SON BL CR for TS 38.473, TP for SON BL CR for TS 38.300, TP for SON BL CR for TS 38.423) MRO Enhancements for LTM and CHO with Candidate SCG(s) |
Nokia |
| R3-251595 |
(TP for SON BL CR for TS 37.340) Reformulation of the forwarding mechanism and MRO Enhancements for optimisation of the S-CPAC selection |
Nokia |
| R3-251695 |
(TP for SON BLCR of 38.473) Discussion on MRO for LTM |
NEC |
| R3-251706 |
(TP for SON BL CR for TS 38.473) Discussion on LTM MRO |
Google |
| R3-251721 |
(TP to BL CR for TS38.473 and TS38.401) MRO for LTM |
Samsung |
| R3-251722 |
(BL CR to 38.420 for SON) Addition of SON enhancements |
Samsung, ZTE, CATT, Lenovo |
| R3-251748 |
(TP for SON BLCR TS38.300, TS37.340 and TS38.423) MRO for CHO with candidate SCGs and S-CPAC |
Samsung, JIO Platforms |
| R3-251749 |
Failure scenarios on MRO for CHO with candidate SCGs |
Samsung, Cybercore, Lenovo |
| R3-251774 |
(TP for 38.473 and 38.401) MRO for Rel-18 LTM |
CATT |
| R3-251775 |
(TP for 37.340, 38.423 and 38.300) MRO for CHO with Candidate SCG(s) and S-CPAC |
CATT |
| R3-251923 |
Ping pong detection and mitigation |
Huawei, China Unicom, CMCC |
| R3-251924 |
Context retrieval |
Huawei, Deutsche Telekom, ZTE, BT |
| R3-251925 |
(TP for SON BLCR for 37.340, 38.423) MRO for others |
Huawei |
| R3-251926 |
(TP for SON BLCR for 38.300, 38.401, 38.473, 38.413) MRO for LTM |
Huawei |
| R3-251932 |
(TP for SON BLCR for 38.473) Discussion on MRO for LTM |
Lenovo |
| R3-251933 |
(TP for SON BLCR for 38.423) Discussion on MRO for subsequent CPAC and CHO with candidate SCG(s) |
Lenovo |
| R3-252048 |
(TP for BL CR to 38.473 for SON) MRO enhancements for LTM |
Ericsson |
| R3-252187 |
Discussion on MRO enhancements for LTM |
CMCC |
| R3-252191 |
(TP for SON BLCR 38.40138.473 38.300 and 38.423)Discussion on MRO |
ZTE Corporation |
| R3-252192 |
(TP for SON BLCR 38.300 and38.473)MRO for LTM- invalid TA |
ZTE Corporation |
| R3-252193 |
(TP for SON BLCR 38.300 38.40138.413 and 38.473) LTM Ping-Pong Avoidance |
ZTE Corporation |
| R3-252246 |
Discussion on MRO Enhancements |
China Unicom |
| R3-252298 |
SoD of MRO for LTM |
Lenovo |
| R3-252299 |
SoD of MRO for others |
Samsung |
| R3-252347 |
(TP for SON BLCR 38.300 )MRO for LTM- outdated TA |
ZTE Corporation |
| R3-252353 |
(TP for SON BL CR for TS38.423) MRO for CHO with Candidate SCG(s) |
Samsung, JIO Platforms |
| R3-252354 |
LS on support of MRO for mobility enhancement |
RAN3(Samsung) |
| R3-252358 |
(TP for SON BL CR for TS38.300) MRO for CHO with Candidate SCG(s) |
CATT |
| R3-252413 |
(TP for SON BL CR for TS38.423) MRO for CHO with Candidate SCG(s) |
Samsung, Jio Platforms, Huawei, ZTE Corporation, Nokia, CATT, Lenovo, Ericsson, Cybercore |
| 10.3.1 |
Intra-NTN Mobility |
|
| R3-251589 |
SON MDT for NTN |
Qualcomm Incorporated |
| R3-251596 |
[TP to BL CR to 38.423, SON] Solution to avoid restarting MRO in NTN deployments |
Nokia |
| R3-251696 |
Discussion on SON/MDT enhancements for NTN |
NEC |
| R3-251726 |
(TP for MDT BLCRs for TS38.413, TS38.423) SON/MDT enhancements for NTN |
Samsung |
| R3-251776 |
(TP for 38.300 and 38.413) Intra-NTN mobility for SONMDT |
CATT |
| R3-251889 |
(TPs to BL CR for 38.300, 38.413 and 38.423) Further discussion on SONMDT enhancements for NTN |
ZTE Corporation |
| R3-251927 |
(TP for SON BLCR for 38.423) MRO for Intra-NTN mobility |
Huawei |
| R3-251934 |
Discussion on MRO for intra-NTN mobility |
Lenovo |
| R3-252049 |
SON-MDT enhancements for NTN |
Ericsson |
| R3-252050 |
(BL CR to 38.413 for SON) Addition of SON enhancements |
Ericsson |
| R3-252121 |
Discussion on SONMDT for Intra-NTN mobility |
Huawei, CMCC, China Unicom |
| R3-252122 |
(TP for MDT BLCR for TS38.413): Logged MDT enhancement for NTN |
Huawei, CMCC, China Unicom |
| R3-252123 |
(TP for MDT BLCR for TS38.423): Logged MDT enhancement for NTN |
Huawei, CMCC, China Unicom |
| R3-252124 |
(TP for MDT BLCR for TS37.320): Logged MDT enhancement for NTN |
Huawei, CMCC, China Unicom |
| R3-252125 |
[DRAFT] LS on SONMDT for NTN |
Huawei, CMCC, China Unicom |
| R3-252167 |
Discussion on SONMDT enhancement for NTN |
CMCC, Huawei |
| R3-252168 |
LS on SONMDT for NTN |
CMCC |
| R3-252249 |
Discussion on SONMDT enhancements for NTN mobility |
China Unicom |
| R3-252300 |
SoD of SONMDT NTN related |
CMCC |
| R3-252341 |
LS on SONMDT for NTN |
RAN3(CMCC) |
| R3-252382 |
LS on SONMDT for NTN |
RAN3(CMCC) |
| 10.3.2 |
Network Slicing |
|
| R3-251590 |
SON MDT for network slicing |
Qualcomm Incorporated |
| R3-251597 |
[MDT TP to BL CR to TS 38.300] Slice-related mobility enhancements |
Nokia |
| R3-251777 |
Network slicing for SONMDT |
CATT |
| R3-251928 |
Network Slicing |
Huawei, Lenovo, Qualcomm |
| R3-252051 |
MDT Enhancements for slice-focused measurements collection |
Ericsson, Jio Platforms (JPL), Deutsche Telekom, AT&T, InterDigital, FiberCop, Orange |
| R3-252052 |
(TP for BL CR to 38.413 for MDT) Deferred MDT for slice-focused measurements collection |
Ericsson, Jio Platforms (JPL), Deutsche Telekom, AT&T, InterDigital, FiberCop |
| R3-252053 |
Data collection for slice coverage observability enhancement |
Ericsson, Jio Platforms, BT, InterDigital, Deutsche Telekom |
| R3-252054 |
Slice-aware user plane interruption times during handovers |
Ericsson, Jio Platforms |
| R3-252086 |
Discussion on the per UE slice enhancements for immediate MDT measurements collection |
Jio Platforms |
| R3-252182 |
Discussion on SON/MDT for network slicing |
CMCC |
| R3-252301 |
SoD of SONMDT slicing related |
ZTE |
| 10.4 |
R18 leftovers |
|
| R3-251750 |
(TP for SON BLCR for TS37.340) Rel-18 SON and MDT leftovers |
Samsung,JIO Platforms |
| R3-251929 |
(TP for SON BLCR for 38.413, 36.423) R18 leftovers |
Huawei |
| R3-251935 |
Discussion on MRO for R18 leftovers |
Lenovo |
| R3-252302 |
SoD of SONMDT leftovers |
Nokia |
| 11.1 |
General |
|
| R3-251544 |
(BL CR to 38.423) Support of enhancements on AI/ML for NG-RAN |
ZTE Corporation, Qualcomm, China Unicom, Ericsson, Samsung, Nokia, Lenovo, CATT, Huawei, NEC, CMCC, China Telecom, Telecom Italia, Deutsche Telekom, Verizon Wireless, LGE, Jio Platforms (JPL), Rakuten, Orange |
| R3-251545 |
(BL CR to 38.473) Support of enhancements on AI/ML for NG-RAN |
Ericsson (Rapporteur), ZTE, NEC, Nokia, Huawei |
| R3-252236 |
Work plan for Rel-19 Enhancements for AI/ML for NG-RAN |
ZTE Corporation, NEC |
| R3-252504 |
(BL CR to 38.423) Support of enhancements on AI/ML for NG-RAN |
ZTE Corporation, Qualcomm, China Unicom, Ericsson, Samsung, Nokia, Lenovo, CATT, Huawei, NEC, CMCC, China Telecom, Telecom Italia, Deutsche Telekom, Verizon Wireless, LGE, Jio Platforms (JPL), Rakuten, Orange |
| R3-252505 |
(BL CR to 38.473) Support of enhancements on AI/ML for NG-RAN |
Ericsson (Rapporteur), ZTE, NEC, Nokia, Huawei |
| 11.2 |
AI/ML enabled Slicing |
|
| R3-251592 |
Enhancement of IEs supporting UE performance feedback between nodes |
Tejas Network Limited |
| R3-251608 |
Discussion on AI/ML assisted Network Slicing |
ZTE Corporation |
| R3-251609 |
[TP to 38.300] AI/ML assisted Network Slicing |
ZTE Corporation, Lenovo, Samsung |
| R3-251610 |
[TP to 38.423] AI/ML assisted Network Slicing |
ZTE Corporation, China Unicom, China Telecom, Qualcomm |
| R3-251627 |
AI/ML enabled slicing |
Ofinno, LLC |
| R3-251675 |
(TP for BLCR for TS38.300) Support of enhancements on AI/ML for NG-RAN |
NEC, ZTE, Qualcomm, Samsung, CMCC |
| R3-251676 |
Open issues for AI/ML-based Slicing |
NEC |
| R3-251677 |
TP to BLCR TS38.423 on AI/ML-based Slicing |
NEC |
| R3-251785 |
Discussion on remaining issues for NG-RAN AI/ML for Network Slicing |
Qualcomm Incorporated |
| R3-251792 |
Discussion on AI/ML enabled slicing |
Samsung |
| R3-251793 |
(TP to BL CR of 38.423) AI-based slicing |
Samsung |
| R3-251823 |
(TP on 38.423)Support of AI/ML enabled Slicing |
CATT |
| R3-251824 |
Support of AI/ML enabled Slicing |
CATT |
| R3-251829 |
Enhancement of UE performance metrics |
CATT,Jio Platforms,Qualcomm,CBN |
| R3-251921 |
AI/ML enabled Network Slicing |
Ericsson, JIO Platforms, Deutsche Telekom |
| R3-251922 |
(TP to TS 38.423) AI/ML enabled Network Slicing |
Ericsson, JIO Platforms, Deutsche Telekom |
| R3-251937 |
Left issues with AI enabled slicing |
Lenovo |
| R3-251982 |
Cell capacity class value for AI/ML enabled slicing |
Ericsson, JIO Platforms, Deutsche Telekom |
| R3-251983 |
(TP to TS 38.423) Cell capacity class value for AI/ML enabled slicing |
Ericsson, JIO Platforms, Deutsche Telekom |
| R3-251989 |
(TP for AI/ML BLCR to TS 38.300) Capturing agreements in Stage 2 RAN specifications |
Huawei, Deutsche Telekom, FiberCop, CATT |
| R3-251990 |
(TP for AI/ML BLCR to TS 38.401) Capturing agreements in Stage 2 RAN specifications |
Huawei, Deutsche Telekom, FiberCop, CATT |
| R3-251991 |
(TP for AI/ML BLCR to TS 37.340) Capturing agreements in Stage 2 RAN specifications |
Huawei, Deutsche Telekom, Qualcomm, FiberCop |
| R3-251992 |
Discussion on AI/ML-based Network Slicing |
Huawei |
| R3-251993 |
(TP for AI/ML BLCR to TS 38.423) XnAP enhancements for AI/ML-based Network Slicing |
Huawei |
| R3-252077 |
AI/ML Slicing Open Issues |
Nokia |
| R3-252078 |
(TP for BLCR to TS 38.423) AI/ML Slicing |
Nokia |
| R3-252173 |
Discussion on AI-based network slice |
CMCC |
| R3-252206 |
New IE in Data Collection Request procedure for UE Performance Data |
Rakuten Mobile, Inc |
| R3-252207 |
UE Performance Granularity for AI/ML based Network Slicing |
Rakuten Mobile, Inc |
| R3-252231 |
TP to TS 38.423 : AI/ML enabled Network Slicing |
Tejas Network Limited |
| R3-252287 |
CB:#AIRAN1_Slicing |
Ericsson |
| R3-252312 |
(TP to TS 38.423) AI/ML enabled Network Slicing |
Ericsson, JIO Platforms, Deutsche Telekom |
| R3-252432 |
(TP to TS 38.423) AI/ML enabled Network Slicing |
Ericsson, JIO Platforms, Deutsche Telekom, ZTE, Huawei, Nokia, Ofinno, NEC, CATT, Tejas Networks, CMCC, LGE, Verizon, Samsung |
| 11.3 |
AI/ML enabled Coverage and Capacity Optimization |
|
| R3-251648 |
(TP for BLCR to TS 38.473) Further discussion on energy efficient AI/ML-based CCO issue prediction in split architecture |
Nokia, FiberCop, Jio Platforms (JPL) |
| R3-251649 |
(TP for BLCR to TS 38.473) Further discussion on signalling for AI/ML-based CCO |
Nokia |
| R3-251678 |
Open issues for AI/ML-based CCO |
NEC |
| R3-251787 |
Discussion on remaining issues in AI/ML enabled CCO |
Qualcomm Incorporated |
| R3-251794 |
Discussion on AI/ML enabled CCO |
Samsung |
| R3-251825 |
(TP on 38.473) Open issues on the CCO use case |
CATT |
| R3-251826 |
Open issues on the CCO use case |
CATT |
| R3-251869 |
Discussion on AI/ML based Coverage and Capacity Optimization |
China Telecom |
| R3-251870 |
(TP for BLCR to TS38.423) Support of AI/ML based Coverage and Capacity Optimization |
China Telecom |
| R3-251871 |
(TP for BLCR to TS38.473) Support of AI/ML based Coverage and Capacity Optimization |
China Telecom |
| R3-251911 |
AIML enabled CCO - Single predicted CCO issue resolution |
Ericsson, InterDigital, Jio Platforms, Deutsche Telekom |
| R3-251912 |
(TP to 38.473) - AIML enabled CCO - Single predicted CCO issue resolution |
Ericsson, InterDigital, Jio Platforms, Deutsche Telekom |
| R3-251913 |
AIML enabled CCO - Prediction validation and timing issues |
Ericsson, InterDigital, Jio Platforms, Deutsche Telekom, FiberCop |
| R3-251914 |
(TP to 38.473) - AIML enabled CCO - Prediction validation and timing issues |
Ericsson, InterDigital, Jio Platforms, Deutsche Telekom, FiberCop |
| R3-251915 |
(TP to 38.423) - AIML enabled CCO - Prediction validation and timing issues |
Ericsson, InterDigital, Jio Platforms, Deutsche Telekom, FiberCop |
| R3-251916 |
AIML enabled CCO - Multiple CCO issues |
Ericsson, InterDigital, Jio Platforms, Deutsche Telekom |
| R3-251917 |
(TP to 38.473) – AIML enabled CCO - Multiple CCO issues |
Ericsson, InterDigital, Jio Platforms, Deutsche Telekom |
| R3-251918 |
(TP to 38.423) - AIML enabled CCO – Multiple CCO issues |
Ericsson, InterDigital, Jio Platforms, Deutsche Telekom |
| R3-251936 |
Discussion on AIML based CCO |
Lenovo |
| R3-251994 |
Discussion on AI/ML-based Coverage and Capacity Optimization |
Huawei, Jio Platforms, Orange, Deutsche Telekom, FiberCop |
| R3-251995 |
(TP for AIML BLCR to TS 38.423) XnAP enhancements for AIML-based Coverage and Capacity Optimization |
Huawei, Jio Platforms, Deutsche Telekom, FiberCop |
| R3-251996 |
(TP for AIML BLCR to TS 38.473) F1AP enhancements for AIML-based Coverage and Capacity Optimization |
Huawei, Jio Platforms, Deutsche Telekom, FiberCop |
| R3-252090 |
Discussion on issues for AI/ML-based CCO |
LG Electronics Inc. |
| R3-252091 |
(TP for NR_AIML_NGRAN_enh-Core for TS 38.473) Discussion on issues for AIML-based CCO |
LG Electronics Inc. |
| R3-252155 |
Discussion on AI/ML assisted Coverage and Capacity Optimization |
ZTE Corporation |
| R3-252156 |
[TP to 38.401] Support of AI/ML assisted CCO |
ZTE Corporation, Lenovo, China Unicom, China Telecom |
| R3-252157 |
[TP to 38.423 and 38.473] Support of AI/ML assisted Coverage and Capacity Optimization |
ZTE Corporation |
| R3-252174 |
Discussion on AI/ML-based CCO |
CMCC |
| R3-252204 |
Coexistence of multiple CCO issues |
Rakuten Mobile, Inc |
| R3-252205 |
Timing Information for AIML based CCO |
Rakuten Mobile, Inc |
| R3-252237 |
[TP to BLCR to TS 38.300] Support of AI/ML assisted CCO |
ZTE Corporation, Lenovo, China Unicom |
| R3-252288 |
CB:#AIRAN2_CCO |
NEC |
| R3-252355 |
(TP for AI/ML BLCR to TS 38.423) Discussion on the AI/ML-based Coverage and Capacity Optimization |
NEC, CATT, ZTE, Ericsson, Deutsche Telekom, Huawei |
| R3-252356 |
(TP for AI/ML BLCR to TS 38.473) Discussion on the AI/ML-based Coverage and Capacity Optimization |
CATT, NEC, ZTE, Ericsson, Deutsche Telekom, Huawei |
| 11.4 |
R18 leftovers |
|
| R3-251529 |
LS reply to LS on energy saving for split gNB |
SA5(Ericsson) |
| R3-251611 |
Discussion on Mobility Optimization for NR-DC |
ZTE Corporation |
| R3-251612 |
(TP to BLCR for TS 38.423) Addition of predicted PSCell ID within DC procedure |
ZTE Corporation, Samsung, Qualcomm, China Unicom, CMCC, CATT, Ofinno |
| R3-251613 |
(TP to BLCR for TS 38.423) Mobility Optimization for NR-DC |
ZTE Corporation |
| R3-251614 |
Discussion on split architecture |
ZTE Corporation |
| R3-251615 |
(TP to BLCR for TS 38.473) Support of EC in case of split architecture |
ZTE Corporation, China Unicom, China Telecom |
| R3-251616 |
(TP to BLCR for TS 37.483) Support of UE performance in case of split architecture |
ZTE Corporation, China Telecom, China Unicom |
| R3-251628 |
Mobility Optimization for NR-DC |
Ofinno, LLC |
| R3-251679 |
Measurement Continuity for continuous MDT collection |
NEC |
| R3-251680 |
(TP to BLCR TS38.423) NR-DC mobility optimization |
NEC |
| R3-251681 |
(TP to BLCR TS38.473) Split architecture support |
NEC |
| R3-251788 |
Discussion on UE Performance Reporting for Split Architecture |
Qualcomm Incorporated |
| R3-251795 |
Discussion on AI/ML for mobility in NR-DC |
Samsung |
| R3-251796 |
Discusson on AI/ML for NG-RAN in split architecture |
Samsung |
| R3-251797 |
(CR to 37.483) AI/ML for NG-RAN on split architecture |
Samsung |
| R3-251827 |
AI/ML in DC scenario |
CATT |
| R3-251828 |
(TP for 37.480 and 38.470) AI/ML in split gNBs |
CATT |
| R3-251865 |
Discussion on AI/ML based Mobility Optimization for NR-DC |
China Telecom |
| R3-251866 |
(TP to TS38.423) Support of AIML based Mobility Optimization for NR-DC |
China Telecom |
| R3-251872 |
(TP for BLCR to TS 38.473) Discussion on signalling energy cost in split architecture |
China Telecom |
| R3-251919 |
AI/ML support for NR-DC |
Ericsson, InterDigital, Jio Platforms |
| R3-251920 |
(TP to TS 38.423) AI/ML support for NR-DC |
Ericsson, InterDigital, Jio Platforms |
| R3-251938 |
Discussion on UE performance metric in AIML for NR-DC |
Lenovo |
| R3-251939 |
Discussion on UE performance collection in split architecture |
Lenovo |
| R3-251940 |
(TP to BLCR 37.340) AIML for NR-DC |
Lenovo, CATT, ZTE Corporation, Samsung |
| R3-251941 |
(TP to BLCR 38.401) AIML for RAN in split architecture |
Lenovo, CATT, ZTE Corporation |
| R3-251975 |
On collection of throughput measurements for UE performance |
Ericsson, Nokia, JIO Platforms |
| R3-251976 |
(TP to 38.473) – Energy Cost signalling support in Split architecture |
Ericsson, Nokia, JIO Platforms, Deutsche Telekom, FiberCop |
| R3-251977 |
On collection of delay measurements for UE performance |
Ericsson, JIO Platforms |
| R3-251978 |
(TP to 38.473) - Delay measurements for UE performance support in Split architecture |
Ericsson, JIO Platforms |
| R3-251979 |
(TP to 37.483) – Delay measurements for UE performance support in Split architecture |
Ericsson, JIO Platforms |
| R3-251980 |
(TP to 37.483) – Throughput measurements for UE performance support in Split architecture |
Ericsson, JIO Platforms |
| R3-251981 |
(TP to 38.425) - Split architecture support for Release 18 use cases |
Ericsson |
| R3-251997 |
(TP for AI/ML BLCR to TS 38.423) Discussion on AI/ML-based Mobility Optimization in NR-DC |
Huawei |
| R3-251998 |
(Draft LS to SA5 on UE performance) Discussion on split architecture support for Rel-18 “AI/ML for NG-RAN” use cases |
Huawei |
| R3-251999 |
(TP for AI/ML BLCR to TS 38.473) F1AP enhancements for split architecture support for Rel-18 “AI/ML for NG-RAN” use cases |
Huawei |
| R3-252000 |
(TP for AI/ML BLCR to TS 37.483) E1AP enhancements for split architecture support for Rel-18 “AI/ML for NG-RAN” use cases |
Huawei |
| R3-252079 |
Energy Saving in Split Architecture |
Nokia, Deutsche Telekom, FiberCop |
| R3-252080 |
[Draft] Reply LS on LS reply to LS on energy saving for split gNB |
Nokia, Deutsche Telekom, FiberCop |
| R3-252081 |
Procedures for AI/ML Mobility Optimization in NR-DC |
Nokia |
| R3-252082 |
(TP for BLCR to TS 38.423) AI/ML Mobility for NR-DC |
Nokia |
| R3-252083 |
(TP for BLCR to TS 38.473, TP for BLCR to TS 37.483) Procedures for Measuring Packet Delay over UP |
Nokia |
| R3-252092 |
Discussion on AI/ML-based mobility optimization for NR-DC |
LG Electronics Inc. |
| R3-252169 |
Discussion on AIML based Mobility Optimization for NR-DC |
CMCC |
| R3-252170 |
(TP to 38.423) AIML based Mobility Optimization for NR-DC |
CMCC |
| R3-252175 |
Discussion on E1/F1 to support UE performance feedback |
CMCC |
| R3-252176 |
Discussion on UE performance metric for both non-split and split architecture |
CMCC |
| R3-252177 |
(TP for BLCR to TS 38.401) OAM Requirements for Energy Saving for split architecture |
CMCC, Samsung, Huawei, NEC, CATT |
| R3-252178 |
(TP to BLCR to TS38.473) Transfer Measured EC via F1 for split architecture |
CMCC, ZTE, CATT, Lenovo, Samsung |
| R3-252290 |
CB:#AIRAN3_SplitArch |
ZTE |
| R3-252291 |
CB:#AIRAN4_NRDC |
Huawei |
| R3-252325 |
(TP for AI/ML BLCR to TS 38.423) AI/ML-based Mobility Optimization in NR-DC |
Huawei |
| R3-252398 |
LS on clarification on UE performance measurement at PDCP level |
RAN3(ZTE) |
| R3-252421 |
(TP for BLCR to TS 37.480) Support of data collection over E1 interface |
Nokia |
| R3-252422 |
(TP for BLCR to TS 37.483) Support of data collection over E1 interface |
Samsung |
| R3-252436 |
LS on clarification on UE performance measurement at PDCP level |
RAN3(ZTE) |
| R3-252441 |
(TP for BLCR to TS 37.483) Support of data collection over E1 interface |
Samsung, ZTE Corporation, Nokia |
| R3-252448 |
(TP for AI/ML BLCR to TS 38.423) AI/ML-based Mobility Optimization in NR-DC |
Huawei, Nokia, LG Electronics, ZTE, Lenovo, Ericsson, Samsung, CMCC |
| R3-252492 |
LS on clarification on UE performance measurement at PDCP level |
RAN3(ZTE) |
| R3-252502 |
(BL CR to 37.480) Support of enhancements on AI/ML for NG-RAN |
CATT |
| R3-252503 |
(BL CR to 37.483) Support of enhancements on AI/ML for NG-RAN |
Samsung |
| 12.1 |
General |
|
| R3-251546 |
(BL CR to 38.410 for Femto) Introduction of NR Femto in NGAP list of functions |
ZTE Corporation, Nokia |
| R3-251547 |
(BL CR to TS 38.413 for Femto) Support of NR Femto architecture with NR Femto Gateway |
Nokia, Huawei |
| R3-251548 |
(BL CR to 38.300 for Femto) Introduction of NR Femto Architecture and Protocol Aspects |
Ericsson, Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, Huawei, LG Electronics, Samsung, Lenovo, Baicells, ZTE, NEC |
| R3-251549 |
(BL CR to 38.305 for WAB) Support of Location Service Involving WAB-Nodes |
ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, Lenovo, CATT, Samsung, Huawei, China Telecom |
| R3-251550 |
Support for Wireless Access Backhaul |
Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung, Lenovo, Qualcomm, Jio Platforms |
| R3-251551 |
(BL CR to 38.413 for WAB) Additional ULI for UEs served by WAB-Nodes |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, China Telecom, ZTE, Qualcomm, Samsung, CATT, Jio Platforms (JPL), Lenovo |
| R3-251552 |
(BL CR to 38.455 for WAB) Support of Location Service Involving WAB-Nodes |
Lenovo, ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, CATT, Samsung, Huawei, China Telecom, Jio Platforms (JPL) |
| R3-252327 |
(BL CR to 38.410 for Femto) Introduction of NR Femto in NGAP list of functions |
ZTE Corporation, Nokia, Baicells |
| R3-252529 |
(BL CR to 38.300 for Femto) Introduction of NR Femto Architecture and Protocol Aspects |
Ericsson, Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, Huawei, LG Electronics, Samsung, Lenovo, Baicells, ZTE, NEC |
| R3-252530 |
(BL CR to 38.401 for WAB) Support for Wireless Access Backhaul |
Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung, Lenovo, Qualcomm, Jio Platforms |
| R3-252531 |
(BL CR to 38.413 for WAB) Additional ULI for UEs served by WAB-Nodes |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, China Telecom, ZTE, Qualcomm, Samsung, CATT, Jio Platforms (JPL), Lenovo |
| 12.2 |
Wireless Access Backhaul (WAB) |
|
| R3-251531 |
LS on MWAB-gNB Configurations |
SA5(Samsung) |
| R3-251583 |
Functional Aspects of WAB-Nodes |
Ericsson, Jio Platforms |
| R3-251584 |
(TP for WAB BL CR for TS 38.401) Functional Aspects of WAB-Nodes |
Ericsson, Jio Platforms |
| R3-251619 |
Remaining aspects of WAB |
Qualcomm Inc. |
| R3-251620 |
WAB radio resource coordination |
Qualcomm Inc. |
| R3-251621 |
BL draft CR to TS 38.300 on Support of WAB |
Qualcomm, Ericsson, CATT, ZTE, Nokia, Nokia Shanghai Bell |
| R3-251637 |
(TP to BLCR for TS 38.401) On support of WAB |
CATT |
| R3-251638 |
(TP to BLCR for TS 38.423) On resource coordination and Xn management for WAB |
CATT |
| R3-251694 |
(TP to BL CR of 38.423 on WAB) Discussion on access and reliability for WAB |
NEC |
| R3-251727 |
(TP to BL CR for TS 38.401) Discussion on NG management and Xn management for WAB |
Nokia, Nokia Shanghai Bell |
| R3-251728 |
(TP for TS 38.423) Enhancement for WAB |
Nokia, Nokia Shanghai Bell |
| R3-251842 |
(TP to BLCR for TS 38.410) Discussion on WAB mobility |
Samsung |
| R3-251843 |
Discussion on other aspects for the support of WAB |
Samsung |
| R3-251850 |
(TPs for WAB BL CRs) Architecture, Access Control and Additional ULI for WAB |
Huawei |
| R3-251851 |
(TP for WAB BL CR for TS 38.401) Radio Resource multiplexing coordination for WAB-node |
Huawei |
| R3-251942 |
(TP to BL CR 38.401) Architecture and configuration for WAB-node |
Lenovo |
| R3-251943 |
(TP to BL CR 38.423) WAB-node co-location discovery |
Lenovo |
| R3-251960 |
Discussion on enhancements for WAB |
CANON Research Centre France |
| R3-252100 |
Further consideration on support of WAB |
LG Electronics |
| R3-252101 |
(TP to TS 38.401, 38.413 and 38.423) TP for WAB support |
LG Electronics |
| R3-252106 |
Discussion on Wireless Access Backhaul |
NTTDOCOMO, INC. |
| R3-252134 |
On Multi-hop Prevention and Functionalities for WAB |
China Telecom |
| R3-252135 |
On RAN2 Impact of WAB |
China Telecom |
| R3-252224 |
(TP to 38.401) Discussion on multi hop prevention and additional ULI for WAB |
ZTE Corporation |
| R3-252225 |
(TP to TS 36.300) Discussion on supporting WAB |
ZTE Corporation |
| R3-252251 |
Discussion on Wireless Access Backhaul |
NTTDOCOMO, INC. |
| R3-252303 |
Summary of Offline Discussion on additional topological enhancement |
NTTDOCOMO, INC. |
| R3-252326 |
CB:#WAB |
NTTDOCOMO, INC. |
| R3-252349 |
(TP for WAB BL CR for TS 38.401) Functional Aspects of WAB-Nodes |
Ericsson, Jio Platforms |
| R3-252392 |
(TP for WAB BL CR for TS 38.413) Adding additional ULI for WAB in NUA procedures |
Huawei |
| R3-252437 |
(TP for TS 38.423) Introduction of WAB-MT Identifier in XnAP |
Nokia, Nokia Shanghai Bell, Ericsson, ZTE, LG Electronics, Qualcomm, Huawei |
| R3-252447 |
(TP for WAB BL CR for TS 38.401) Functional Aspects of WAB-Nodes |
Ericsson, Jio Platforms |
| R3-252455 |
(TP for WAB BL CR for TS 38.401) Functional Aspects of WAB-Nodes |
Ericsson, Jio Platforms, Samsung, Qualcomm, Lenovo, Nokia |
| R3-252456 |
(TP for WAB BL CR for TS 38.413) Adding additional ULI for WAB in NUA procedures |
Huawei, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, Samsung |
| R3-252458 |
(TP for TS 38.423) Introduction of WAB-MT Identifier in XnAP |
Nokia, Nokia Shanghai Bell, Ericsson, ZTE, LG Electronics, Qualcomm, Huawei, China Telecom, Samsung, Lenovo |
| R3-252465 |
(TP for WAB BL CR for TS 38.401) Functional Aspects of WAB-Nodes |
Ericsson, Huawei, China Telecom, Samsung, Qualcomm, Lenovo, Nokia, Nokia Shanghai Bell, ZTE Corporation, Jio Platforms |
| R3-252532 |
(BL CR to 38.423) Introduction of WAB-MT Identifier in XnAP |
Nokia, Nokia Shanghai Bell |
| 12.3 |
5G Femto |
|
| R3-251524 |
LS on NR Femto node shared by PLMN and PNI-NPN |
SA2(LGE) |
| R3-251622 |
(TP to draft BL CR to TS 38.300) Discussion on NR Femto node shared by PLMN and PNI-NPN |
Qualcomm Inc. |
| R3-251639 |
Discussion on remain issue of NR Femto |
CATT |
| R3-251640 |
(TP to BLCR for TS 38.300) Introduction of Functional Split for NR Femto |
CATT |
| R3-251682 |
Mobility for NR Femto |
NEC |
| R3-251702 |
(TP to TS 38.300) Discussion on function split for NR Femto |
ZTE Corporation |
| R3-251703 |
Discussion on access control for NR Femto |
ZTE Corporation |
| R3-251786 |
Discussion on Slice Feature and Access Control for NR Femto |
Baicells Technologies Co. Ltd |
| R3-251789 |
TP to BL CR for TS 38.300 and TS 38.413 on NR Femto |
Baicells Technologies Co. Ltd |
| R3-251844 |
(TP to TS 38.300) Discussion on functional split for NR Femto |
Samsung |
| R3-251845 |
(draft Reply LS to SA2) Discussion on LS from SA2 for NR Femto |
Samsung |
| R3-251852 |
(TP for Femto BL CR for TS 38.300/38.413) Discussion on functional split and remaining issues for NR Femto |
Huawei |
| R3-251853 |
(TP for Femto BL CR for TS 38.300) Discussion on SA2's LS on NR Femto node shared by PLMN and PNI-NPN |
Huawei |
| R3-251861 |
On remaining issues for NR Femto |
China Telecom |
| R3-251900 |
IP Version Selection when the NR Femto GW Is Deployed |
Ericsson LM |
| R3-251901 |
Sharing between PLMN and PNI-NPN |
Ericsson LM |
| R3-251944 |
Discussion on remaining issues for NR Femto |
Lenovo |
| R3-251945 |
(TP to BL CR 38.300) Architecture and function split for NR Femto |
Lenovo |
| R3-252012 |
Completion of Functional Aspects of NR Femto |
Nokia, BT |
| R3-252013 |
Reply LS on NR Femto Node shared by PLMN and PNI NPN |
Nokia |
| R3-252102 |
(TP to TS 38.300) Further discussion on access control in 5G Femto |
LG Electronics |
| R3-252103 |
[Draft] Reply LS on NR Femto node shared by PLMN and PNI-NPN |
LG Electronics |
| R3-252107 |
Discussion on 5G femto |
NTTDOCOMO, INC. |
| R3-252252 |
Discussion on 5G femto |
NTTDOCOMO, INC. |
| R3-252289 |
(TP to BL CR to 38.300 for Femto) clarification of shared NR Femto |
Nokia |
| R3-252296 |
Reply LS on NR Femto node shared by PLMN and PNI-NPN |
RAN3(LGE) |
| R3-252333 |
(TP to BL CR to 38.300 for Femto) clarification of shared NR Femto |
Nokia, Verizon Wireless, TMO US, LG Electronics, Baicells, Huawei, Qualcomm Incorporated, Samsung, Lenovo, ZTE, Ericsson |
| R3-252337 |
Reply LS on NR Femto node shared by PLMN and PNI-NPN |
RAN3(LGE) |
| 13.1 |
General |
|
| R3-251553 |
(BL CR to 38.420) Support for Inter-CU LTM |
ZTE Corporation, China Telecom, Samsung, Nokia, CATT, NEC, LG Electronics, Ericsson, Huawei, Lenovo |
| R3-251554 |
(BL CR to 37.340) stage 2 for inter-CU LTM in NR-DC |
CATT, China Telecom, Huawei, Nokia, LG Electronics, Google, Samsung, Ofinno, Ericsson, Lenovo, NEC, ZTE |
| R3-251555 |
(BL CR to 37.483) Introducing Rel-19 Mobility enhancement |
LG Electronics Inc., Nokia, China Telecom, Google, Ericsson, CATT, Qualcomm, Samsung, CMCC, ZTE, Huawei, NTT Docomo, Lenovo, NEC, Ofinno, Jio Platforms (JPL) |
| R3-251556 |
(BL CR to 38.300) Support for Inter-CU LTM |
Nokia, Huawei, Google, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung, Offino |
| R3-251557 |
(BL CR to 38.401) on conditional intra-CU LTM |
China Telecom, ZTE Corporation, NEC, Samsung, Nokia, Google, Huawei, Ericsson, LG Electronics |
| R3-251558 |
(BL CR to 38.423) Xn support for inter-CU LTM |
Ericsson, Samsung, Nokia, China Telecom, CATT, Huawei, Google, Lenovo, NEC, ZTE, LG Electronics, Ofinno |
| R3-251559 |
(BL CR to 38.473) Inter-CU LTM |
Huawei, Nokia, Samsung, Google, NEC, China Telecom, Ericsson, LG Electronics, CATT, Ofinno, ZTE, Lenovo |
| R3-252516 |
(BL CR to 37.340) stage 2 for inter-CU LTM in NR-DC |
CATT, China Telecom, Huawei, Nokia, LG Electronics, Google, Samsung, Ofinno, Ericsson, Lenovo, NEC, ZTE |
| R3-252517 |
(BL CR to 38.300) Support for Inter-CU LTM |
Nokia, Huawei, Google, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung, Offino |
| R3-252518 |
(BL CR to 38.401) on conditional intra-CU LTM |
China Telecom, ZTE Corporation, NEC, Samsung, Nokia, Google, Huawei, Ericsson, LG Electronics |
| R3-252519 |
(BL CR to 38.420) Support for Inter-CU LTM |
ZTE Corporation, China Telecom, Samsung, Nokia, CATT, NEC, LG Electronics, Ericsson, Huawei, Lenovo |
| R3-252520 |
(BL CR to 38.423) Xn support for inter-CU LTM |
Ericsson, Samsung, Nokia, China Telecom, CATT, Huawei, Google, Lenovo, NEC, ZTE, LG Electronics, Ofinno |
| R3-252522 |
(BL CR to 38.473) Inter-CU LTM |
Huawei, Nokia, Samsung, Google, NEC, China Telecom, Ericsson, LG Electronics, CATT, Ofinno, ZTE, Lenovo |
| 13.2 |
Support for inter-CU LTM |
|
| R3-251507 |
LS on activation/deactivation of semi-persistent CSI-RS resource for LTM candidate cells |
RAN1(Fujitsu) |
| R3-251525 |
Reply LS on security handling for inter-CU LTM in non-DC cases |
SA3(CATT) |
| R3-251533 |
TP (BL CR TS 38.300) Inter-CU LTM Procedure |
Nokia |
| R3-251582 |
Discussion on Inter-CU LTM security |
Nokia |
| R3-251629 |
Data forwarding for Inter-CU LTM DC scenarios |
Ofinno, LLC |
| R3-251630 |
Issues on SN initiated inter-CU SCG LTM |
Ofinno, LLC |
| R3-251633 |
Discussion on Inter-CU LTM |
Rakuten Mobile, Inc |
| R3-251670 |
(TP to BL CR for TS 38.423 on Inter-CU LTM) Rel-19 inter-CU LTM issues |
NEC |
| R3-251671 |
discussion Rel-19 inter-CU LTM in DC scenario |
NEC |
| R3-251707 |
(TP to BL CR 38.423) Support subsequent mobility in inter-CU LTM |
Google |
| R3-251741 |
(TP for NR_Mob_Ph4 TS 38.473) Discussions on key distribution and NCC delivery for Inter-CU LTM |
LG Electronics Inc. |
| R3-251742 |
Discussions on key remaining aspects of Inter-CU LTM |
LG Electronics Inc. |
| R3-251759 |
Signalling enhancements for Inter-CU LTM handover |
Qualcomm Incorporated |
| R3-251835 |
(TP for 38.473, 38.423) Discussion for security handling on non-DC case |
CATT |
| R3-251836 |
[Draft LS] Reply LS to SA3 on the security handling for inter-CU LTM in non-DC case |
CATT |
| R3-251837 |
(TP for 37.340) Discussion for Inter-CU LTM |
CATT |
| R3-251862 |
Discussion on signaling enhancement for inter-CU LTM |
China Telecom |
| R3-251863 |
(TP to TS38.401) Support of activation or deactivation of SP CSI-RS for inter-DU LTM |
China Telecom |
| R3-251881 |
(TP for 38.423, 38.300, 38.420, 38.470) Inter-CU LTM |
ZTE Corporation |
| R3-251946 |
[TP to BLCR for TS 38.423] Inter-CU LTM |
Lenovo |
| R3-251947 |
[TP to BLCR for TS 38.423] Inter-CU LTM in DC |
Lenovo |
| R3-251963 |
Further discussion on inter-CU LTM |
Ericsson |
| R3-251964 |
(TP for LTM BL CR for TS 38.423, TS 38.473, TS 38.300, TS 37.340) – Support for inter-CU LTM |
Ericsson |
| R3-251971 |
gNB-DU initiated LTM candidate cell reconfiguration |
Rakuten Mobile, Inc |
| R3-251972 |
gNB-DU initiated LTM candidate cell reconfiguration |
Rakuten Mobile, Qualcomm Inc |
| R3-251986 |
Issues on source gNB initiated LTM cancel and UE association setup |
Ofinno, LLC |
| R3-252088 |
Support for Inter-CU L1/L2 Triggered Mobility (LTM) over Xn |
Jio Platforms Ltd (JPL) |
| R3-252089 |
Xn support for inter-CU L1/L2 Triggered Mobility |
Jio Platforms Ltd (JPL) |
| R3-252118 |
(TP for LTM BLCR for TS38.473, TS38.300, TS38.470): Further discussion on inter-CU LTM procedure |
Huawei |
| R3-252119 |
(TP for LTM BLCR for TS37.340, TS38.423): Discussion on inter-CU SCG LTM |
Huawei |
| R3-252148 |
Discussion on inter-CU LTM |
NTT DOCOMO INC.. |
| R3-252152 |
Discussion on inter-gNB-CU LTM |
Samsung |
| R3-252153 |
(TP to BLCR for TS38.423 and TS38.473) Inter-gNB-CU LTM |
Samsung |
| R3-252228 |
CSI-RS network coordination |
Ericsson, Nokia, LG Electronics |
| R3-252229 |
(TP for TS 38.423) – Xn support for Semi-persistent CSI-RS transmission |
Ericsson, Nokia, LG Electronics |
| R3-252230 |
(TP for TS 38.473) – F1 support for Semi-persistent CSI-RS transmission |
Ericsson, Nokia, LG Electronics |
| R3-252240 |
(TP for 38.423, 37.340) SN initiate SCG LTM |
ZTE Corporation |
| R3-252261 |
Response to R3-251582 and R3-251881 |
vivo |
| R3-252305 |
Summary of offline discussion on inter-CU LTM |
China Telecom |
| R3-252320 |
CB:MobilityENh_LTM |
China Telecom |
| R3-252424 |
(TP to BL CR TS 38.300) Inter-CU LTM Procedure |
Nokia |
| R3-252431 |
(TP for LTM BL CR for TS 38.423) – Further agreements on inter-CU LTM |
Ericsson, Nokia, Samsung, CATT, China Telecom, Ofinno, LG Electronics, Lenovo, Huawei |
| R3-252433 |
(TP for LTM BLCR for TS38.473) Update on inter-CU LTM procedure |
Huawei |
| R3-252434 |
(TP for LTM BLCR for TS 38.470) Introduce inter-CU LTM procedure |
Huawei, LG Electronics, Samsung, Ericsson, China Telecom, Nokia, ZTE Corporation, CATT |
| R3-252438 |
(TP to TS38.401) Support of activation or deactivation of SP CSI-RS for inter-DU LTM |
China Telecom, Nokia, Samsung, Ericsson, ZTE, Huawei, CATT |
| R3-252439 |
(TP for 37.340) Discussion for Inter-CU LTM |
CATT |
| R3-252440 |
Reply LS to SA3 on the security handling for inter-CU LTM in non-DC case |
RAN3(CATT) |
| R3-252444 |
(TP for BLCR to 38.420) Inter-CU LTM |
ZTE Corporation, Nokia, Samsung, China Telecom, Ericsson, Huawei, LG Electronics, CATT |
| R3-252445 |
[TP to BLCR for TS 38.423] Inter-CU LTM in DC |
Lenovo |
| R3-252449 |
Reply LS to SA3 on the security handling for inter-CU LTM in non-DC case |
RAN3(CATT) |
| R3-252457 |
(TP to BL CR TS 38.300) Inter-CU LTM Procedure |
Nokia |
| R3-252461 |
(TP to BL CR for 38.423 DC) Inter-CU LTM in DC |
Lenovo, Ericsson, CATT, Huawei, Ofinno, Nokia, NEC, LGE, China Telecom, Google, ZTE, Samsung |
| R3-252462 |
(TP for LTM BLCR for TS37.340): TP for Inter-CU LTM |
CATT, China Telecom, Huawei, Nokia, LG Electronics, Google, Samsung, Ofinno, Ericsson, Lenovo, NEC, ZTE, Qualcomm |
| R3-252463 |
(TP for LTM BLCR for TS38.473) Update on inter-CU LTM procedure |
Huawei, LG Electronics, Samsung, Nokia, China Telecom, NEC, Ericsson, ZTE Corporation |
| R3-252482 |
(TP to BL CR TS 38.300) Inter-CU LTM Procedure |
Nokia, Samsung, Huawei, Ericsson, LG Electronics, CATT, Ofinno, ZTE, NEC, China Telecom, Qualcomm |
| R3-252483 |
(TP for LTM BLCR for TS 38.470) Introduce inter-CU LTM procedure |
Huawei, LG Electronics, Samsung, Ericsson, China Telecom, Nokia, ZTE Corporation, CATT |
| R3-252521 |
(BL CR to 38.470) Support for inter-CU LTM procedure |
Samsung |
| R3-252541 |
(BL CR to 38.423 for DC) Xn support for inter-CU LTM in DC |
Lenovo (Shanghai) Information |
| 13.3 |
Support for Conditional LTM |
|
| R3-251534 |
Discussion on Conditional LTM in disaggregated gNB architecture |
Nokia |
| R3-251672 |
(TP to BL CR for TS 38.401and 38.473 on conditional intra-CU LTM) Discussion of Rel-19 intra-CU Conditional LTM |
NEC |
| R3-251743 |
(TP for TS 38.401 and TS 38.473) Discussions on RAN3 impacts from Conditional Intra-CU LTM |
LG Electronics Inc. |
| R3-251760 |
Signalling enhancements for Conditional Intra-CU LTM |
Qualcomm Incorporated |
| R3-251838 |
(TP to 38.473)Discussion for C-LTM |
CATT |
| R3-251864 |
(TP for TS38.401) On support of intra-CU Conditional LTM |
China Telecom |
| R3-251882 |
(TP for LTM BLCR for TS38.401) Conditional intra-SN LTM |
ZTE Corporation |
| R3-251948 |
[TP to BLCR for TS 38.401] Conditional intra-CU LTM |
Lenovo |
| R3-251965 |
(TP to CLTM BL CR for TS 38.473, TS 38.401) – Further discussion on Intra-CU Conditional LTM |
Ericsson |
| R3-252120 |
(TP for LTM BLCR for TS38.473, TS38.401): Discussion on intra-CU conditional LTM |
Huawei |
| R3-252164 |
Discussion on Intra-CU Conditional LTM |
Samsung |
| R3-252321 |
CB:Mobility_CLTM |
Nokia |
| R3-252423 |
(TP for LTM BLCR for TS38.401) Conditional intra-SN LTM |
ZTE Corporation, LG Electronics, Nokia, Lenovo, China Telecom, Huawei |
| R3-252435 |
(TP for LTM BLCR for TS38.473) Support of intra-CU conditional LTM |
Huawei, Nokia, LG Electronics, Ericsson, Google, ZTE Corporation, China Telecom, Lenovo, NEC |
| 14.1 |
General |
|
| R3-251560 |
(BL CR to 38.410) Introduce NG Removal procedure |
CMCC, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Qualcomm, Xiaomi, LG Electronics, China Telecom, Samsung, ZTE, NEC, ETRI |
| R3-251561 |
(BL CR to 38.300) Support for Regenerative Payload and MBS broadcast in NR NTN |
Ericsson, Thales, Deutsche Telekom, Nokia, ESA, CATT, ZTE, Sateliot, Huawei, Dish Networks, Echostar, Eutelsat Group, Xiaomi, Samsung, CMCC, LG Electronics, NEC, Lenovo, ETRI |
| R3-251562 |
Support for Regenerative Payload and MBS broadcast in NR NTN |
CATT, Thales, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, Qualcomm, Samsung, Xiaomi, CMCC, China Telecom, Jio, LG Electronics, NEC, ETRI, SES, ESA |
| R3-251712 |
Updated work plan for NR_NTN_Ph3 |
CATT, Thales |
| R3-252523 |
(BL CR to 38.300) Support for Regenerative Payload and MBS broadcast in NR NTN |
Ericsson, Thales, Deutsche Telekom, Nokia, ESA, CATT, ZTE, Sateliot, Huawei, Dish Networks, Echostar, Eutelsat Group, Xiaomi, Samsung, CMCC, LG Electronics, NEC, Lenovo, ETRI |
| R3-252524 |
(BL CR to 38.410) Introduce NG Removal procedure |
CMCC, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Qualcomm, Xiaomi, LG Electronics, China Telecom, Samsung, ZTE, NEC, ETRI |
| R3-252525 |
(BL CR to 38.413) Support for Regenerative Payload and MBS broadcast in NR NTN |
CATT, Thales, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, Qualcomm, Samsung, Xiaomi, CMCC, China Telecom, Jio, LG Electronics, NEC, ETRI, SES, ESA |
| 14.2 |
Support MBS broadcast service |
|
| R3-251685 |
(TP for TS 38.413) Discussion on NR NTN supporting MBS broadcast service |
NEC |
| R3-251713 |
Clarification on MBS broadcast service area |
CATT |
| R3-251729 |
(TP to BL CR for TS 38.300 and TS 38.413) Update on the support of MBS Broadcast Service |
Nokia, Nokia Shanghai Bell, Qualcomm |
| R3-251811 |
Remaining issue on support broadcast service for NR NTN |
Samsung |
| R3-251890 |
Further discussion on NTN broadcast service supporting |
ZTE Corporation |
| R3-252104 |
Signaling of Intended MBS Broadcast Service Area via NR NTN |
Jio Platforms (JPL) |
| R3-252105 |
Support for Broadcast Service Area Signaling in NGAP |
Jio Platforms Ltd (JPL) |
| R3-252343 |
(TP to BL CR for TS 38.413) Update on the support of MBS Broadcast Service |
Nokia, Nokia Shanghai Bell, Qualcomm, Huawei, Ericsson, Samsung, CATT, ZTE, NEC |
| 14.3 |
Support of Regenerative payload |
|
| R3-251528 |
Reply LS to LS on reply to LS on OAM requirements to support regenerative payload |
SA5(Huawei) |
| R3-251594 |
Further Discussion on Support of NTN Regenerative Architecture |
TCL |
| R3-251686 |
(TP for TS 38.300) Discussion on regenerative payload enhancement for NR NTN |
NEC |
| R3-251714 |
(TP to NTN BL CRs) Support of Regenerative payload |
CATT |
| R3-251730 |
(TP to BL CR for TS 38.413) Discussion on the support of Regenerative payload |
Nokia, Nokia Shanghai Bell |
| R3-251731 |
(TP to BL CR for TS 38.413) Enhancement to support hard FLSO |
Nokia, Nokia Shanghai Bell, Qualcomm, Xiaomi, China Telecom |
| R3-251744 |
Discussions on INACTIVE support from moving satellite gNBs |
LG Electronics Inc. |
| R3-251745 |
(TP for NR_NTN_Ph3 TS 38.300 BL CR) OAM for NG management |
LG Electronics Inc. |
| R3-251766 |
Support of Inactive UE mobility in NTN |
Xiaomi, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-251767 |
(TP for TS 38.300) Support of regenerative payload |
Xiaomi |
| R3-251772 |
TP for TS 38.300 on NR NTN Regenerative Payload Feeder Link Switch Over |
Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Xiaomi, CATT |
| R3-251784 |
(TP for TS 38.300) Discussion on Hard FLSO and RRC Inactive state in NR NTN Regenerative Payload |
Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Xiaomi, China Telecom |
| R3-251812 |
Further discussion on support of regenerative payload for NR NTN |
Samsung |
| R3-251873 |
(TP for TS 38.300) Support of regenerative payload |
China Telecom |
| R3-251891 |
(TP to BL CR for 38.413) Further discussion on support of regenerative payload |
ZTE Corporation |
| R3-251902 |
Considerations on NG Interface Management over the Feeder Link |
Ericsson, Thales, Huawei, Jio Platforms Limited, Intelsat, ESA |
| R3-251903 |
Making the Case for Location-Based CHO in Rel-19 |
Ericsson, Thales, ESA, Inmarsat, Viasat, Jio Platforms Limited, Intelsat |
| R3-251904 |
Location-Based CHO in Rel-19 - XnAP Impacts |
Ericsson, Thales, ESA, Inmarsat, Viasat, Jio Platforms Limited, Intelsat |
| R3-251905 |
Inactive UEs and NR NTN |
Ericsson, Jio Platforms Limited, T-Mobile, BT, Thales, Telia Company, China Unicom, KT Corp. |
| R3-252009 |
(TP for TS 38.300) Support of regenerative payload-UE INACTIVE |
Huawei |
| R3-252010 |
(TP for TS 38.300) Support of regenerative payload - various topics |
Huawei |
| R3-252073 |
Tracking Area Handling for Regenerative Satellite Access |
Ericsson LM |
| R3-252074 |
Study for RRC-INACTIVE UEs in NR NTN |
Jio Platforms |
| R3-252099 |
Discussion on Support of Inactive UE in NTN |
ETRI |
| R3-252179 |
Discussion on Support of regenerative payload for NR NTN |
CMCC |
| R3-252180 |
(TPs to BL CR 38.410) Introduce NG Removal Function |
CMCC, Samsung, ZTE, CATT |
| R3-252211 |
Discussion on support of regenerative payload for NR NTN |
CSCN |
| R3-252348 |
CB:#NRNTN |
Xiaomi |
| R3-252405 |
(TP for TS 38.300) Support of regenerative payload - Stage 2 on TNL management |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Xiaomi, CATT, Samsung, CMCC, ZTE Corporation, Qualcomm Incorporated |
| R3-252408 |
(TP to BL CR for TS 38.300) Enhancement to support hard FLSO |
Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Xiaomi, China Telecom |
| R3-252409 |
(TP to BL CR for TS 38.413) Enhancement to support hard FLSO |
Nokia, Nokia Shanghai Bell, Qualcomm, Xiaomi, China Telecom, CATT, Samsung, ZTE Corporation, LG Electronics, NEC |
| R3-252416 |
(TPs to BL CR 38.410) Introduce NG Removal Function |
CMCC, Samsung, ZTE, CATT, Xiaomi, Nokia, Nokia Shanghai Bell, LG Electronics, NEC, China Telecom |
| R3-252419 |
(TP to BL CR for TS 38.300) Support of feeder link switch |
CATT |
| R3-252452 |
(TP for TS 38.300) Support of regenerative payload - Stage 2 on TNL management |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Xiaomi, CATT, Samsung, CMCC, ZTE Corporation, Qualcomm Incorporated, NEC, China Telecom, LG Electronics |
| R3-252453 |
(TP to BL CR for TS 38.300) Support of feeder link switch |
CATT, Samsung, Huawei, Nokia, Nokia Shanghai Bell, Ericsson, ZTE Corporation, LG Electronics, NEC, CMCC, Xiaomi, China Telecom, Jio |
| R3-252454 |
(TP to BL CR for TS 38.300) Enhancement to support hard FLSO |
Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Xiaomi, China Telecom, CATT, Samsung, ZTE Corporation, LG Electronics, NEC |
| 15.2 |
Support Full eNB as Regenerative Payload |
|
| R3-251768 |
Support of full eNB as regenerative payload |
Xiaomi |
| R3-252109 |
Seamless Feeder Link Switch-Over Support for Regenerative Payload Operation |
Jio Platforms Ltd (JPL) |
| R3-252110 |
Introduction of UE Context Suspend/Resume procedures |
Jio Platforms Ltd (JPL) |
| 16.1 |
General |
|
| R3-251526 |
Reply to LS on A-IoT Conclusions in SA WG2 |
SA5(China Unicom) |
| R3-251563 |
(BL CR to 38.300) Introduction of Ambient IoT |
CMCC, Huawei |
| R3-251564 |
(BL CR to 38.410) Introduction of Ambient IoT |
ZTE Corporation, China Telecom, Huawei, Samsung, CMCC, Nokia, Xiaomi |
| R3-251565 |
Introduction of Ambient IoT |
Huawei |
| R3-252292 |
(BL CR to 38.413) Introduction of Ambient IoT |
Huawei |
| R3-252293 |
(BL CR to 38.300) Introduction of Ambient IoT |
CMCC, Huawei |
| R3-252294 |
(BL CR to 38.410) Introduction of Ambient IoT |
ZTE Corporation, China Telecom, Huawei, Samsung, CMCC, Nokia, Xiaomi |
| R3-252493 |
(BL CR to 38.300) Introduction of Ambient IoT |
CMCC, Huawei |
| R3-252496 |
(BL CR to 38.413) Introduction of Ambient IoT |
Huawei |
| 16.2 |
RAN Architecture and Procedures |
|
| R3-251585 |
Architecture, Protocols and Signaling to support Topology 1 of A-IoT |
Qualcomm Incorporated |
| R3-251586 |
Inventory and Command procedures for Topology 1 of A-IoT |
Qualcomm Incorporated |
| R3-251603 |
(TPs to TS 38.300 38.413 BL CRs) Architecture aspects and interface management procedures |
Huawei |
| R3-251604 |
(TPs to TS 38.413 38.410 BL CRs) Support of Inventory |
Huawei |
| R3-251605 |
(TPs to TS 38.413 38.410 BL CRs) Support of Command |
Huawei |
| R3-251660 |
Conclusion on Ambient IoT Architecture |
Nokia |
| R3-251661 |
[TP for BL CR AIoT for TS 38.413] Additions for AIoT protocol |
Nokia |
| R3-251662 |
Signalling Information Elements for Inventory |
Nokia |
| R3-251663 |
Signalling Information Elements for Command |
Nokia |
| R3-251687 |
Discussion on AIoT architecture aspects |
NEC |
| R3-251688 |
Discussion on AIoT procedures aspects |
NEC |
| R3-251715 |
(TP to BL CR for TS38.300) A-IoT protocol stack |
CATT |
| R3-251716 |
(TP to BL CR for TS38.413) A-IoT inventory and command procedures |
CATT |
| R3-251717 |
Discussion on A-IoT reader selection |
CATT |
| R3-251762 |
Discussion on support of AIoT |
Xiaomi |
| R3-251763 |
(TP for TS 38.413) Support of AIoT |
Xiaomi |
| R3-251764 |
(BL CR for TS 38.412) Support of AIoT |
Xiaomi |
| R3-251765 |
Discussion on location of the device |
Xiaomi |
| R3-251791 |
(TP for TS 38.412) Support of Ambient IoT |
Xiaomi, Huawei, CMCC |
| R3-251813 |
Discussion on RAN architecture and procedures for AIoT |
Samsung |
| R3-251949 |
On A-IOT Inventory Procedure |
Lenovo |
| R3-251950 |
On A-IOT Command Procedure |
Lenovo |
| R3-252056 |
[TP for BL CR 38.401 and 38.300] Multiplexing several A-IoT service operations concerning multiple A-IoT devices on NG-C and other architectural topics |
Ericsson |
| R3-252057 |
[TP for BL CR 38.413] Applicability of NG Interface management procedures for A-IoT |
Ericsson |
| R3-252058 |
[TP for BL CR 38.300] AIoT service area indication |
Ericsson |
| R3-252059 |
[TP for BL CR 38.413 and 38.300 and 38.410] Introducing A-IoT protocol functions in NGAP |
Ericsson |
| R3-252116 |
Ambient IoT support |
Jio Platforms Ltd (JPL) |
| R3-252165 |
Signalling Procedure for Inventory and Command |
China Telecom |
| R3-252183 |
(TP to TS 38.300) Discussion on RAN Architecture for Ambient IoT |
CMCC |
| R3-252184 |
Discussion on Inventory Procedure and Signaling |
CMCC |
| R3-252185 |
Discussion on Command Procedure and Signalling |
CMCC |
| R3-252241 |
(TP for BL CR to 38.300, 38.413, 38.410) Leftover issues on AIoT |
ZTE Corporation, China Telecom |
| R3-252242 |
(TP for BL CR 38.413) New AIoT procedures |
ZTE Corporation, China Telecom |
| R3-252243 |
(TP to BL CR 38.300, 38.410) New Ambient IoT procedures |
ZTE Corporation, China Telecom |
| R3-252297 |
CB:_AIoT1_Procedures |
Huawei |
| R3-252328 |
(TP to TS 38.300 BL CR) Architecture aspects |
CMCC, Huawei, Nokia, NEC |
| R3-252329 |
(TP to TS 38.300 BL CR) Update of Inventory and Command call flows |
Nokia |
| R3-252330 |
(TP to BL CR for TS38.300) A-IoT protocol stack |
CATT |
| R3-252331 |
(TP to TS 38.300 BL CR) Device Locating support |
ZTE Corporation, China Telecom, Nokia, Huawei, CATT |
| R3-252332 |
(TP to TS 38.401 BL CR) Device Association aspects |
Lenovo, Huawei |
| R3-252334 |
(TP to TS 38.412 BL CR) SCTP association |
Xiaomi, Huawei, CMCC |
| R3-252335 |
(TP to TS 38.413 BL CR) Updates of the Inventory and command |
Huawei, ZTE Corporation |
| R3-252336 |
(TP to TS 38.413 BL CR) Interface management |
Ericsson, Nokia, Huawei, CATT, ZTE Corporation |
| R3-252338 |
[Draft] LS on RAN3 Ambient IoT progress |
RAN3(Huawei) |
| R3-252459 |
(TP for BL CR AiOT for TS 38.300) Update of inventory and command |
Nokia, Huawei, CMCC, NEC |
| R3-252477 |
(TP to TS 38.300 BL CR) Device Locating support |
ZTE Corporation, China Telecom, Nokia, Huawei, CATT |
| R3-252478 |
(TP to TS 38.401 BL CR) Device Association aspects |
Lenovo, Huawei |
| R3-252479 |
(TP to TS 38.412 BL CR) SCTP association |
Xiaomi, Huawei, CMCC |
| R3-252480 |
(TP to TS 38.413 BL CR) Updates of the Inventory and command |
Huawei, ZTE Corporation |
| R3-252481 |
LS on Ambient IoT further progress of RAN3 |
RAN3(Huawei) |
| R3-252494 |
(BL CR to 38.401) Introduction of Ambient IoT |
Ericsson |
| R3-252495 |
(BL CR to 38.412) Introduction of Ambient IoT |
Xiaomi |
| 16.3 |
Location Report |
|
| R3-251587 |
Locating Ambient IoT devices |
Qualcomm Incorporated |
| R3-251606 |
(TPs to TS 38.300 38.413 BL CRs) Support of Device Locating |
Huawei |
| R3-251689 |
Discussion on AIoT location reporting aspects |
NEC |
| R3-251718 |
Discussion on locating of A-IoT device |
CATT |
| R3-251814 |
Discussion on Location report for AIoT |
Samsung |
| R3-252186 |
(TP to TS 38.300) Discussion on A-IoT device location reporting |
CMCC |
| R3-252244 |
TP to (BL CR to 38.300) Location AIoT device |
ZTE Corporation, China Telecom |
| R3-252248 |
Discussion on support of location report |
LG Electronics |
| 17.1 |
General |
|
| R3-251566 |
(BL CR to 38.473) Introduction of Network Energy Saving Enhancement |
Huawei, Ericsson, CMCC, Samsung, ZTE, Nokia, Deutsche Telekom, Lenovo, NEC, Jio |
| R3-251567 |
Introduction of Network Energy Saving Enhancement |
Ericsson, Huawei, CMCC, Samsung, Qualcomm, Nokia, ZTE, Lenovo, Deutsche Telekom, NEC |
| R3-252019 |
WI Work plan for R19 Network Energy Savings |
Ericsson |
| R3-252307 |
Introduction of Network Energy Saving Enhancement |
Ericsson, Huawei, CMCC, Samsung, Qualcomm, Nokia, ZTE, Lenovo, Deutsche Telekom, NEC |
| R3-252498 |
(BL CR to 38.423) Introduction of Network Energy Saving Enhancement |
Ericsson, Huawei, CMCC, Samsung, Qualcomm, Nokia, ZTE, Lenovo, Deutsche Telekom, NEC |
| R3-252499 |
(BL CR to 38.473) Introduction of Network Energy Saving Enhancement |
Huawei, Ericsson, CMCC, Samsung, ZTE, Nokia, Deutsche Telekom, Lenovo, NEC, Jio |
| 17.2 |
Support on-demand SSB SCell operation |
|
| R3-251623 |
Aspects of on-demand SSB for NES enhancements |
Qualcomm Inc. |
| R3-251642 |
(TP for BLCR to TS 38.423, 38.473) On support of OD-SSB |
CATT |
| R3-251650 |
Open points on OD-SSB. Adaptation of common signals/channels |
Nokia |
| R3-251683 |
Support on-demand SSB operation |
NEC |
| R3-251723 |
Discussion on on-demand SSB SCell operation in low-carbon green network |
Samsung |
| R3-251751 |
(TP to BLCR for TS 38.473 and TS 38.470) Discussion on on-demand SSB SCell operation |
Huawei |
| R3-251860 |
(TP to 38.473) On support on-demand SSB SCell operation |
China Telecom |
| R3-251892 |
(TP to BL CR for 38.473) Further discussion on on-demand SSB Scell operation |
ZTE Corporation |
| R3-251951 |
Discussion on On-demand SSB for SCell |
Lenovo |
| R3-252041 |
Discussion on On-Demand SSB SCell Operation |
CMCC |
| R3-252044 |
On-demand SSB SCell operation |
Ericsson |
| R3-252117 |
XnAP Enhancements for UL WUS Configuration in On-Demand SIB1 |
Jio Platforms Ltd (JPL) |
| R3-252357 |
CB: # ES1_OndemandSSB |
Huawei |
| 17.3 |
Support on-demand SIB1 for UEs |
|
| R3-251624 |
Aspects of on-demand SIB1 for NES enhancements |
Qualcomm Inc. |
| R3-251641 |
(TP to BLCR for TS 38.300) Introduction of OD-SIB1 |
CATT, Ericsson, Huawei, Samsung, China Telecomm, Rakuten, ZTE, CMCC, Lenovo |
| R3-251643 |
(TP to BLCR for F1AP) On support of OD-SIB1 for idle UE |
CATT, Fujitsu |
| R3-251651 |
(TP for BLCR to TS 38.423, TS 38.300) Stage 2 and stage 3 Proposals for On-Demand SIB1 |
Nokia |
| R3-251684 |
Support on-demand SIB1 |
NEC |
| R3-251724 |
Discussion on on-demand SIB1 in low-carbon green network |
Samsung |
| R3-251725 |
Introduction of Network Energy Saving Enhancement |
Samsung, Huawei, NEC, CATT, ZTE, Ericsson |
| R3-251752 |
(TP to BLCR for TS 38.473 and TS 38.423) Discussion on on-demand SIB1 for UEs in idle or inactive mode |
Huawei |
| R3-251848 |
Xn impact of On-demand SIB1 for UEs in idle/inactive mode |
Ericsson, Deutsche Telekom, China Unicom, Jio Platforms |
| R3-251849 |
F1 impact of On-demand SIB1 for UEs in idle/inactive mode |
Ericsson, Deutsche Telekom, China Unicom, Jio Platforms |
| R3-251893 |
(TP to BL CR for 38.423) Further discussion on on-demand SIB1 |
ZTE Corporation |
| R3-251952 |
(TP to BL CR 38.423 and 38.473) Discussion on On-demand SIB1 for Idle/Inactive UE |
Lenovo |
| R3-252042 |
(TPs to BL CRs) Support On-Demand SIB1 for UEs |
CMCC |
| R3-252208 |
Support for OD-SIB1 mechanism at Cell A and NES Cell |
Rakuten Mobile, Inc |
| R3-252210 |
Signalling to support OD-SIB1 |
Rakuten Mobile, Inc |
| R3-252385 |
(TP to BLCR for TS 38.423) On-demand SIB1 for Ues in idle/inactive mode |
Ericsson, Deutsche Telekom, China Unicom, Jio Platforms |
| R3-252386 |
(TP to BLCR for TS 38.473) On-demand SIB1 for Ues in idle or inactive mode |
Huawei |
| R3-252387 |
CB: # ES2 (Summary of offline discussion) |
Ericsson |
| R3-252450 |
(TP to BLCR for TS 38.300) Introduction of OD-SIB1 |
CATT, Ericsson, Huawei, Samsung, China Telecomm, Rakuten, ZTE, CMCC, Lenovo, Deutsche Telekom |
| R3-252451 |
Introduction of Network Energy Saving Enhancement |
Samsung, Huawei, NEC, CATT, ZTE, Ericsson |
| R3-252466 |
(TP to BLCR for TS 38.473) On-demand SIB1 for Ues in idle or inactive mode |
Huawei, Ericsson, CATT, Samsung, Deutsche Telekom, Qualcomm, NEC, CMCC, ZTE |
| R3-252467 |
(TP to BLCR for TS 38.423) On-demand SIB1 for Ues in idle/inactive mode |
Ericsson, Deutsche Telekom, China Unicom, Jio Platforms, Samsung, Huawei, NEC,CMCC, ZTE, CATT |
| R3-252468 |
(TP to BLCR for TS 38.300) Introduction of OD-SIB1 |
CATT, Ericsson, Huawei, Samsung, China Telecomm, Rakuten, ZTE, CMCC, Lenovo, Deutsche Telekom |
| R3-252469 |
(BL CR to 38.470) Introduction of Network Energy Saving Enhancement |
Samsung, Huawei, NEC, CATT, ZTE, Ericsson |
| R3-252497 |
(BL CR to 38.300) Introduction of Network Energy Saving Enhancement |
CATT |
| 17.4 |
Others |
|
| R3-251517 |
LS on paging enhancement in R19 NES |
RAN2(Xiaomi) |
| R3-251753 |
(TP to BLCR for TS 38.473) Discussion on common signal adaptation |
Huawei, CATT, CMCC |
| R3-251894 |
(TP to BL CR for 38.473) Discussion on UE capability for paging adaptation |
ZTE Corporation, CATT, Lenovo |
| R3-251895 |
[Draft] Reply LS on paging enhancement in R19 NES |
ZTE Corporation, CATT, Lenovo |
| R3-252047 |
Adaptation of common signal/channel transmissions |
Ericsson |
| R3-252310 |
CB:#ES3 |
ZTE |
| R3-252361 |
(TP to BL CR for 38.473) Discussion on UE capability for paging adaptation |
ZTE Corporation, CATT, Lenovo |
| 18.1 |
General |
|
| R3-251568 |
(BL CR to 38.470) Introduction of low-power wake-up signal and receiver for NR |
Nokia, Samsung, ZTE, Ericsson, Huawei, CATT |
| R3-251569 |
(BL CR to 38.473) Introduction of low-power wake-up signal and receiver for NR |
Huawei, Nokia, Samsung, Ericsson, CATT, ZTE, Vivo, NTT DOCOMO INC. |
| R3-251570 |
(BL CR to 38.300) Introduction of low-power wake-up signal and receiver for NR |
vivo, NTT DOCOMO INC., Nokia, Samsung, Ericsson, ZTE, CATT, Huawei |
| R3-251571 |
(BL CR to 38.423) Introduction of low-power wake-up signal and receiver for NR |
Ericsson, Vivo, NTT Docomo, Huawei, ZTE, Nokia, Samsung, CATT |
| R3-251572 |
(BL CR to 38.413) Introduction of low-power wake-up signal and receiver for NR |
ZTE Corporation, Nokia, Samsung, Ericsson, Huawei, CATT, NTT |
| R3-252514 |
(BL CR to 38.300) Introduction of low-power wake-up signal and receiver for NR |
vivo, NTT DOCOMO INC., Nokia, Samsung, Ericsson, ZTE, CATT, Huawei |
| R3-252515 |
(BL CR to 38.473) Introduction of low-power wake-up signal and receiver for NR |
Huawei, Nokia, Samsung, Ericsson, CATT, ZTE, Vivo, NTT DOCOMO INC. |
| 18.2 |
Support LP-WUS Indicating Paging Monitoring |
|
| R3-251515 |
Reply LS on LP-WUS subgrouping |
RAN2(Huawei) |
| R3-251625 |
Support LP-WUS subgrouping in RRC_IDLE/RRC_INACTIVE |
Qualcomm Inc. |
| R3-251644 |
(TP to BL CR for TS 38.410) Potential impacts of LP-WUS |
CATT |
| R3-251645 |
(draft) LS on LP-WUS subgrouping |
CATT |
| R3-251664 |
Conclusions on RAN3 Impacts of LP-WUS |
Nokia |
| R3-251665 |
[TP for BL CR LP-WUS TS 38.473] Conclusions for LP-WUS |
Nokia |
| R3-251693 |
Discussion on LP-WUS UE-ID |
NEC |
| R3-251698 |
Discussion on remaining issues for LP-WUS |
ZTE Corporation |
| R3-251699 |
(TP to TS 38.413) on support of LP-WUS |
ZTE Corporation |
| R3-251754 |
(TP to BLCR for TS 38.413 and TS 38.423 and TS 38.300) Discussion on Low-power wake-up signal and receiver for NR |
Huawei |
| R3-251755 |
(TP to BLCR for TS 38.473) Discussion on Low-power wake-up signal and receiver for NR |
Huawei |
| R3-251756 |
[draft] Reply LS on LP-WUS subgrouping |
Huawei |
| R3-252023 |
Support of Low power radio WUS |
Ericsson |
| R3-252024 |
(TP for LP-WUS BL CR for TS38.423) Removal of FFS |
Ericsson |
| R3-252147 |
Discussion on LP-WUS |
NTT DOCOMO INC.. |
| R3-252181 |
(TP to 38.473)Discussion on supporting LP-WUS Indicating Paging Monitoring |
CMCC |
| R3-252209 |
Remaining Issues on LP-WUS subgrouping |
Samsung |
| R3-252340 |
CB:#LP_WUS |
NTTDoCoMo |
| R3-252342 |
[TP for BL CR LP-WUS TS 38.473] Conclusions for LP-WUS |
Nokia, Huawei |
| R3-252362 |
(TP to BLCR for TS 38.300) Discussion on Low-power wake-up signal and receiver for NR |
Huawei, Ericsson, ZTE, Nokia, CATT |
| 19.1 |
General |
|
| R3-252212 |
Updated workplan for Evolution of NR Duplex Operation |
Huawei, Samsung |
| 19.2 |
Support CLI Handling |
|
| R3-251652 |
Further discussion on network support for SBFD operation and CLI management |
Nokia |
| R3-251697 |
Discussion on CLI handling support |
NEC |
| R3-251758 |
Signaling design to enable NR SBFD operation |
Qualcomm Incorporated |
| R3-251778 |
Discussion on Evolution of Duplex Operation |
CATT |
| R3-251779 |
(TP for 38.420, 38.423, 37.340 and 38.473) Support SBFD Operation |
CATT |
| R3-251798 |
Discussion on information exchanges among gNBs for CLI handling |
Samsung |
| R3-251799 |
TP to BLCR of TS38.473 on CLI handling |
Samsung |
| R3-251831 |
Discussion on Information exchange for SBFD |
ZTE corporation |
| R3-251832 |
(TP for BLCR 38.300&401&420&423&473) SBFD |
ZTE corporation |
| R3-251909 |
Discussion on RAN3 impacts to support enhancements for CLI handling for SBFD |
Ericsson |
| R3-251910 |
TP to TS38.423 on enhancements for CLI handling for SBFD |
Ericsson |
| R3-252055 |
CLI mitigation and CLI testing using new Xn messages and procedures |
Charter Communications, Inc |
| R3-252093 |
Discussion on issues of CLI handling in SBFD |
LG Electronics Inc. |
| R3-252094 |
(TP for NR_duplex_evo-Core for TS 38.423) Discussion on issues on CLI handling in SBFD |
LG Electronics Inc. |
| R3-252171 |
Discussion on supporting CLI handling in SBFD |
CMCC |
| R3-252172 |
(TP for TS 38.423) Support CLI handling |
CMCC |
| R3-252213 |
Further discussions on SBFD related information exchange |
Huawei, China Telecom, China Unicom |
| R3-252214 |
Stage 2&3 CR on the introduction of Evolution of NR duplex operation: Sub-band full duplex (SBFD) |
Huawei |
| R3-252215 |
Stage 2&3 CR on the introduction of Evolution of NR duplex operation: Sub-band full duplex (SBFD) |
Huawei |
| R3-252223 |
Enhancements for Cross-Link Interference Management in NR Duplex Evolution (F1AP interface) |
Jio Platforms Ltd (JPL) |
| R3-252311 |
CB:#SBFD |
Huawei |
| R3-252389 |
(TP to BL CR for 38.423) introduction of Evolution of NR duplex operation: Sub-band full duplex (SBFD) |
Huawei |
| R3-252426 |
(TP to BL CR 38.420) introduction of Evolution of NR duplex operation Sub-band full duplex (SBFD) |
CMCC, Ericsson |
| R3-252428 |
(TP to BL CR for 38.470) introduction of Evolution of NR duplex operation Sub-band full duplex (SBFD) |
CATT, Ericsson |
| R3-252430 |
(TP to BL CR for 38.401) introduction of Evolution of NR duplex operation: Sub-band full duplex (SBFD) |
ZTE Corporation, Ericsson, Samsung |
| R3-252442 |
(TP to BL CR for 38.300) introduction of Evolution of NR duplex operation: Sub-band full duplex (SBFD) |
Ericsson, Huawei |
| R3-252446 |
(TP to BL CR for 38.473) introduction of Evolution of NR duplex operation Sub-band full duplex (SBFD) |
Samsung, Huawei |
| R3-252470 |
(TP to BL CR for 38.423) introduction of Evolution of NR duplex operation: Sub-band full duplex (SBFD) |
Huawei, China Telecom, China Unicom, China Mobile, Ericsson, Qualcomm, Samsung, ZTE Corporation, LG Electronics, Nokia, Jio Platforms (JPL), CATT |
| R3-252471 |
(TP to BL CR 38.420) introduction of Evolution of NR duplex operation Sub-band full duplex (SBFD) |
CMCC, Ericsson, Huawei, Samsung, ZTE, Nokia |
| R3-252472 |
(TP to BL CR for 38.473) introduction of Evolution of NR duplex operation Sub-band full duplex (SBFD) |
Samsung, Huawei, Ericsson, ZTE, LGE, Nokia, Qualcomm |
| R3-252473 |
(TP to BL CR for 38.470) introduction of Evolution of NR duplex operation Sub-band full duplex (SBFD) |
CATT, Ericsson, CMCC, Nokia, ZTE, Qualcomm |
| R3-252474 |
(TP to BL CR for 38.300) introduction of Evolution of NR duplex operation: Sub-band full duplex (SBFD) |
Ericsson, Huawei, Samsung, Qualcomm, ZTE, Huawei, CATT, Nokia, CMCC, LGE |
| R3-252475 |
(TP to BL CR for 38.401) introduction of Evolution of NR duplex operation: Sub-band full duplex (SBFD) |
ZTE Corporation, Ericsson, Samsung, Qualcomm, Huawei, CATT, Nokia, CMCC, LGE |
| R3-252506 |
(BL CR to 38.300) introduction of Evolution of NR duplex operation |
Ericsson |
| R3-252507 |
(BL CR to 38.401) introduction of Evolution of NR duplex operation |
ZTE Corporation |
| R3-252508 |
(BL CR to 38.420) introduction of Evolution of NR duplex operation |
ZTE Corporation |
| R3-252509 |
(BL CR to 38.423) introduction of Evolution of NR duplex operation |
Huawei |
| R3-252510 |
(BL CR to 38.470) introduction of Evolution of NR duplex operation |
CATT |
| R3-252511 |
(BL CR to 38.473) introduction of Evolution of NR duplex operation |
Samsung |
| 20.1 |
General |
|
| R3-251508 |
Reply LS on LMF-based AI/ML Positioning for Case 2b |
RAN1(vivo) |
| R3-252025 |
Work Plan for Rel-19 on AI/ML for PHY (Positioning) |
Ericsson (Rapporteur) |
| 20.2 |
Support Positioning Accuracy Enhancements |
|
| R3-251509 |
Reply LS on LMF-based AI/ML Positioning for Case 3b |
RAN1(Ericsson) |
| R3-251510 |
LS on AI/ML Positioning Case 3b |
RAN1(Ericsson) |
| R3-251617 |
[TP to 38.455 & 38.401] Support of AI/ML assisted Positioning (case 3a) |
ZTE Corporation |
| R3-251618 |
(TP to BLCR to TS 38.455 & TS38.473) Discussion on AI/ML assisted positioning (case 3b) |
ZTE Corporation |
| R3-251692 |
Discussion on AIML based Positioning Accuracy Enhancements |
NEC |
| R3-251719 |
(TP to BL CR for TS38.455) Support of LMF-based AI positioning |
CATT |
| R3-251720 |
(TP to BL CRs) Support of gNB-based AI positioning |
CATT |
| R3-251769 |
(TP for TS 38.455) Support of gNB-side model (case 3a) |
Xiaomi |
| R3-251770 |
(TP for 38.455 and TS 38.473) Support of Sample-based measurement for LMF-side model (case 3b) |
Xiaomi, Ericsson |
| R3-251800 |
Discussion on Case 3a in AI/ML for positioning |
Samsung, JIO Platforms |
| R3-251801 |
Discussion on Case 3b in AI/ML for positioning |
Samsung, JIO Platforms |
| R3-251867 |
Discussion on support of direct AI/ML positioning (Case 3b) |
China Telecom |
| R3-251868 |
Discussion on support of AI/ML assisted positioning (Case 3a) |
China Telecom |
| R3-251953 |
AIML for gNB assisted positioning |
Lenovo |
| R3-251957 |
AI/ML based positioning accuracy enhancements |
Qualcomm Incorporated |
| R3-252001 |
(TP for AI/ML BLCR to TS 38.455) Discussion on RAN3 impacts for Direct AI/ML positioning (Case 3b) |
Huawei |
| R3-252002 |
(TP for AI/ML BLCR to TS 38.455) Discussion on RAN3 impacts for NG-RAN node-assisted AI/ML positioning (Case 3a) |
Huawei |
| R3-252026 |
[DRAFT] LS reply on AI/ML Positioning Case 3b |
Ericsson |
| R3-252027 |
Discussion on data collection procedures to support gNB-sided model (case 3a) |
Ericsson |
| R3-252028 |
(TPs to NRPPa and NGAP BL CRs to support case 3a) |
Ericsson |
| R3-252034 |
(TPs To BL CRs) Support Direct AI ML Positioning |
CMCC |
| R3-252035 |
Support Assisted AI ML Positioning |
CMCC |
| R3-252084 |
(TP to TS 38.305) Model training at gNB for Case 3a |
Nokia |
| R3-252085 |
(TP to TS 38.300) Intermediate feature reporting and general principles for case 3a |
Nokia |
| R3-252154 |
AI/ML-Enhanced Positioning Enhancements for NRPPa |
Jio Platforms Ltd (JPL) |
| R3-252163 |
Model training/monitoring at gNB for Case 3a |
CEWiT, Tejas Networks |
| R3-252306 |
CB:#AIPHY |
CATT |
| R3-252418 |
LS reply on AI/ML Positioning Case 3b |
RAN3(Ericsson) |
| R3-252420 |
(TP to TS 38.305) Model training at gNB for Case 3a |
CATT, Ericsson, Nokia, Huawei, Xiaomi, ZTE |
| R3-252427 |
(TP for BL CR TS 38.455) Support of Sample-based measurement for LMF-side model (case 3b) |
Xiaomi, Ericsson |
| R3-252443 |
[DRAFT] LS on AI/ML Positioning Case 3b |
RAN3(Ericsson) |
| R3-252476 |
[DRAFT] LS on AI/ML Positioning Case 3b |
RAN3(Ericsson) |
| R3-252484 |
(TP for BL CR TS 38.455) Support of Sample-based measurement for LMF-side model (case 3b) |
Xiaomi, Ericsson, ZTE, Huawei, CEWiT, Samsung, CATT, CMCC, Nokia |
| R3-252485 |
LS reply on AI/ML Positioning Case 3b |
RAN3(Ericsson) |
| R3-252486 |
(TP to TS 38.305) Model training at gNB for Case 3a |
CATT, Ericsson, Nokia, Huawei, Xiaomi, ZTE, CMCC, Samsung, CEWiT |
| R3-252487 |
LS on AI/ML Positioning Case 3b |
RAN3(Ericsson) |
| R3-252500 |
(BL CR to 38.305) Introduction of AI/ML air |
CATT |
| R3-252501 |
(BL CR to 38.455) Introduction of AI/ML air |
Ericsson |
| R3-252542 |
LS on AI/ML Positioning Case 3a |
RAN3(Ericsson) |
| 21.1 |
General |
|
| R3-251577 |
(BL CR to 37.340) Support of XR enhancements |
ZTE Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Inc, Lenovo, Huawei, Ericsson, CATT, CMCC, Samsung, Xiaomi, NEC |
| R3-251578 |
(BL CR to 38.300) Support of XR enhancements |
Nokia, Nokia Shanghai Bell, Lenovo, Qualcomm, Xiaomi, CATT, Ericsson, CMCC, Samsung, Huawei |
| R3-251579 |
(BL CR to 38.423) Support of XR enhancements |
CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei, CMCC, NEC |
| R3-251580 |
(BL CR to 38.425) Support of XR enhancements |
Ericsson, AT&T, BT, T-Mobile USA, Charter Communications, Qualcomm, Huawei, Nokia, Nokia Shanghai BellChina Telecom, CMCC, ZTE, CATT |
| R3-251581 |
(BL CR to 38.473) Support of XR enhancements |
Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi, Nokia, Nokia Shanghai Bell, China Telecom |
| R3-251732 |
Rapporteur Inputs on workplan |
Nokia, Qualcomm (Rapporteurs) |
| R3-252533 |
(BL CR to 37.340) Support of XR enhancements |
ZTE Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Inc, Lenovo, Huawei, Ericsson, CATT, CMCC, Samsung, Xiaomi, NEC |
| R3-252535 |
(BL CR to 38.300) Support of XR enhancements |
Nokia, Nokia Shanghai Bell, Lenovo, Qualcomm, Xiaomi, CATT, Ericsson, CMCC, Samsung, Huawei |
| R3-252538 |
(BL CR to 38.423) Support of XR enhancements |
CATT, Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Qualcomm, Huawei, CMCC, NEC |
| R3-252539 |
(BL CR to 38.425) Support of XR enhancements |
Ericsson, AT&T, BT, T-Mobile USA, Charter Communications, Qualcomm, Huawei, Nokia, Nokia Shanghai BellChina Telecom, CMCC, ZTE, CATT |
| R3-252540 |
(BL CR to 38.473) Support of XR enhancements |
Huawei, Ericsson, Lenovo, CMCC, Qualcomm, Xiaomi, Nokia, Nokia Shanghai Bell, China Telecom |
| 21.3 |
Others |
|
| R3-251513 |
LS on uplink rate control |
RAN2(Nokia) |
| R3-251523 |
LS reply on multi-modality awareness |
SA2(Chinamobile) |
| R3-251631 |
Support of Multi-Modality Awareness for XR |
Ofinno, LLC |
| R3-251632 |
Support of Alternative PDU Set QoS for XR in DC scenario |
Ofinno, LLC |
| R3-251673 |
Discussion on MMSID reception in gNB |
NEC |
| R3-251674 |
MMSID reception in gNB |
NEC |
| R3-251733 |
Discussion on the new RAN3 related objectives |
Nokia, Nokia Shanghai Bell |
| R3-251734 |
(TP to BL CR for TS 38.300) Addition of MMSID |
Nokia, Nokia Shanghai Bell, Huawei, CMCC, ZTE, Lenovo |
| R3-251735 |
(TP to BL CR for TS 38.413) enhancement for DL PDU Set marking without PDU Set QoS, and Alternative PDU Set QoS with PSDB and PSER |
Nokia, Nokia Shanghai Bell, CMCC, Huawei, CATT |
| R3-251736 |
(TP to BL CR for TS 38.413) enhancement for available data rate report |
Nokia, Nokia Shanghai Bell, CMCC, Huawei, CATT |
| R3-251737 |
[DRAFT] Reply LS on LS on uplink rate control |
Nokia, Nokia Shanghai Bell |
| R3-251738 |
(TP to BL CR for TS 38.300) Support for Burst Size and TTNB |
Nokia, Nokia Shanghai Bell |
| R3-251757 |
R19 XR Signaling Enhancements |
Qualcomm Incorporated |
| R3-251780 |
Disccsion on NR XR Enhancements for others |
CATT |
| R3-251781 |
(TP to XR BL CR for 38.423) Support of PDU set based QoS handling enhancement |
CATT, Nokia, Nokia Shanghai Bell, CMCC, Huawei |
| R3-251782 |
(TP to XR BL CR for 38.423) Support of available data rate report |
CATT, Nokia, Nokia Shanghai Bell, CMCC, Huawei |
| R3-251830 |
Discussion on Multimodality and uplink congestion |
CANON Research Centre France |
| R3-251833 |
Discussion on multi-modality awareness for QoS flows |
vivo |
| R3-251834 |
Discussion on XR rate control |
vivo |
| R3-251846 |
Discussion on other aspects for NR XR enhancements |
Samsung |
| R3-251847 |
(TP to BLCR for TS 38.473) NR XR enhancements |
Samsung |
| R3-251854 |
(TP for XR BL CR for TS 37.340) Support for ECN marking status change |
Huawei, CMCC, CATT, Nokia, Nokia Shanghai Bell, BT, Vodafone, ZTE, Lenovo |
| R3-251855 |
(TP for XR BL CR for TS38.413) Addition of MMSID |
Huawei, Ericsson, ZTE, Qualcomm, CMCC, Nokia, Nokia Shanghai Bell, CATT, China Telecom, Lenovo |
| R3-251856 |
Discussion on multi-modality awareness and UL rate control |
Huawei |
| R3-251857 |
(TP for XR BL CRs) Discussion on the miscellaneous issues for XR |
Huawei |
| R3-251954 |
Discussion on XR Enhancements |
Lenovo |
| R3-251955 |
Discussion on bit rate control and unnecessary retransmission |
Lenovo |
| R3-252029 |
TP for XR BL CR for TS38.423) Addition of MMSID |
Ericsson, Qualcomm, Huawei, CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, China Telecom, Lenovo |
| R3-252030 |
(TP for XR BL CR for TS38.413) Support of PDU Set QoS enhancement |
Ericsson |
| R3-252031 |
Discussion on XR Bitrate control over F1 |
Ericsson |
| R3-252036 |
(TP to BL CR for TS 38.415 ) Support of QoS Handling Enhancement and Exposure of Available Data Rate |
CMCC |
| R3-252037 |
Support of Uplink Congestion Signalling and PDU Set Based QoS Handling Enhancement |
CMCC |
| R3-252038 |
(TP to BL CR for TS 38.473) Addition of MMSID |
CMCC, Ericsson, Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, China Telecom, Lenovo |
| R3-252039 |
(TP to BL CR for TS 37.483) Support of Alternative PDU Set QoS |
CMCC, Nokia, Nokia Shanghai Bell, Huawei, CATT, Xiaomi |
| R3-252040 |
(TP to BL CR for TS 37.483) Support of Available Data Rate Report |
CMCC, Nokia, Nokia Shanghai Bell, Huawei, CATT, Xiaomi |
| R3-252108 |
(TP to TS 38.415) enhancement for BSSize, TTNB and available data rate |
China Telecom, Nokia, Nokia Shanghai Bell |
| R3-252142 |
(TP for XR BL CR for TS 38.473) Support of PDU set based QoS handling enhancement |
Huawei, Nokia, Nokia Shanghai Bell, CMCC, CATT |
| R3-252143 |
(TP for XR BL CR for TS 38.473) Support of available data rate report |
Huawei, Nokia, Nokia Shanghai Bell, CMCC, CATT |
| R3-252160 |
Discussion on XR Enhancement with draft reply LS |
ZTE Corporation |
| R3-252161 |
[TP for XR BL CR for TS 37.483] Addition of MMSID |
ZTE Corporation, Ericsson, China Telecom, Qualcomm Incorporated, CMCC, CATT, Huawei, Nokia, Nokia Shanghai Bell, Lenovo |
| R3-252162 |
[TP for XR BL CR for TS 38.300, 38.413, 38.423, 38.473,37.483,38.415, 38.425, 38.420, 38.470] Rel-19 additional XR enhancements |
ZTE Corporation |
| R3-252226 |
Discussion on Multi-modality Awareness for XR |
Meta |
| R3-252227 |
Discussion on XR UL Rate Control |
Meta |
| R3-252250 |
Discussion on Rate Control Singalling over F1 Interface |
China Telecom |
| R3-252304 |
Summary of offline discussion on XR |
Nokia, Nokia Shanghai Bell |
| R3-252350 |
(TP for XR BL CR for TS 37.340) Support for ECN marking status change |
Huawei, CMCC, CATT, Nokia, Nokia Shanghai Bell, BT, Vodafone, ZTE, Lenovo, Ericsson |
| R3-252351 |
(TP to BL CR for TS 38.300) Addition of MMSID |
Nokia, Nokia Shanghai Bell, Huawei, CMCC, ZTE, Lenovo, NEC, Ericsson, Samsung, Meta, Qualcomm, CATT |
| R3-252352 |
CB:#XR |
Nokia |
| R3-252363 |
(TP to BL CR for TS 38.413) Support of PDU set based QoS handling enhancement |
NEC, Nokia, Nokia Shanghai Bell, CMCC, Huawei, CATT, China Telecom, ZTE, Ericsson, Qualcomm, Samsung |
| R3-252364 |
(TP to BL CR for TS 38.423) Support of PDU set based QoS handling enhancement |
CATT, Nokia, Nokia Shanghai Bell, CMCC, Huawei, Ofinno, ZTE, Ericsson, Qualcomm |
| R3-252365 |
(TP to BL CR for TS 38.473) Support of PDU set based QoS handling enhancement |
Huawei, Nokia, Nokia Shanghai Bell, CMCC, CATT, Ofinno, China Telecom, ZTE, Ericsson |
| R3-252366 |
(TP to BL CR for TS 37.483) Support of PDU set based QoS handling enhancement |
CMCC, Nokia, Nokia Shanghai Bell, Huawei, CATT, Xiaomi, Ofinno, China Telecom, ZTE, Ericsson, Qualcomm, Samsung |
| R3-252367 |
(TP to BL CR for TS 37.340) Support of PDU set based QoS handling enhancement |
Ofinno, Nokia, Nokia Shanghai Bell, China Telecom |
| R3-252369 |
(TP to TS 38.415) enhancement for BSSize, TTNB and available data rate |
China Telecom, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-252370 |
(TP to BL CR for TS 38.300) enhancement for BSSize and TTNB |
Qualcomm Inc, Nokia, Nokia Shanghai Bell, CMCC, Huawei, China Telecom, ZTE, Lenovo, Ericsson |
| R3-252371 |
(TP to BL CR for TS 38.413) enhancement for available data rate report |
Nokia, Nokia Shanghai Bell, CMCC, Huawei, CATT, China Telecom, ZTE, Ericsson, Qualcomm, Samsung |
| R3-252372 |
(TP to BL CR for TS 38.423) Support of available data rate report |
CATT, Nokia, Nokia Shanghai Bell, CMCC, Huawei, China Telecom, ZTE, Ericsson, Qualcomm |
| R3-252373 |
(TP to BL CR for TS 38.473) Support of available data rate report |
ZTE Corporation, Huawei, Nokia, Nokia Shanghai Bell, CMCC, CATT, China Telecom, Ericsson |
| R3-252374 |
(TP to BL CR for TS 37.483) Support of Available Data Rate Report |
Samsung, CMCC, Nokia, Nokia Shanghai Bell, Huawei, CATT, China Telecom, ZTE, Ericsson |
| R3-252375 |
(TP to BL CR for TS 38.413) Addition of MMSID |
Huawei, Ericsson, ZTE, Qualcomm, CMCC, Nokia, Nokia Shanghai Bell, CATT, China Telecom, Lenovo, Ofinno, Samsung |
| R3-252376 |
(TP to BL CR for TS 38.423) Addition of MMSID |
Ericsson, Qualcomm, Huawei, CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, China Telecom, Lenovo, Ofinno, Samsung |
| R3-252377 |
(TP to BL CR for TS 38.473) Addition of MMSID |
CMCC, Ericsson, Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, China Telecom, Lenovo, Xiaomi, Samsung |
| R3-252378 |
(TP to BL CR for TS 37.483) Addition of MMSID |
ZTE Corporation, Ericsson, China Telecom, Qualcomm Incorporated, CMCC, CATT, Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Samsung |
| R3-252379 |
(TP to BL CR for TS 38.413) Support of uplink rate control |
Lenovo |
| R3-252380 |
(TP to BL CR for TS 38.423) Support of uplink rate control |
Ericsson |
| R3-252381 |
[DRAFT] Reply LS on LS on uplink rate control |
RAN3(Meta) |
| R3-252388 |
(TP to TS 38.425) enhancement for BSSize, TTNB and available data rate |
China Telecom, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-252464 |
[DRAFT] Reply LS on LS on uplink rate control |
RAN3(Meta) |
| R3-252488 |
(TP to TS 38.415) enhancement for BSSize, TTNB and available data rate |
China Telecom, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CMCC, Ericsson, Samsung |
| R3-252489 |
(TP to BL CR for TS 38.413) Support of uplink rate control |
Lenovo, Nokia, Nokia Shanghai Bell, CMCC, China Telecom, Huawei, ZTE, Ericsson, Samsung, Qualcomm |
| R3-252490 |
(TP to BL CR for TS 38.423) Support of uplink rate control |
Ericsson, Nokia, Nokia Shanghai Bell, CMCC, China Telecom, Huawei, ZTE, Qualcomm Inc., Samsung |
| R3-252491 |
Reply LS on uplink rate control |
RAN3(Meta) |
| R3-252534 |
(BL CR to 37.483) Support of XR enhancements |
CMCC |
| R3-252536 |
(BL CR to 38.413) Support of XR enhancements |
Lenovo |
| R3-252537 |
(BL CR to 38.415) Support of XR enhancements |
China Telecom |
| 22.1 |
General |
|
| R3-251573 |
(BL CR to 38.401) Support of Multi-hop relay |
LG Electronics Inc., ZTE, Nokia, Nokia Shanghai Bell, Ericsson, FirstNet, Huawei |
| R3-251574 |
(BL CR to 38.413) Support of Multi-hop relay |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, LG Electronics, NEC, CATT, InterDigital, Samsung, ZTE, FirstNet, NIST |
| R3-251575 |
(BL CR to 38.423) Support of Multi-hop relay |
Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell, Huawei, NEC, CATT, InterDigital, Samsung, ZTE, FirstNet, NIST |
| R3-251576 |
(BL CR to 38.473) Support of Multi-hop relay |
Huawei, LG Electronics, Nokia, Nokia Shanghai Bell, NEC, CATT, Ericsson, Samsung, ZTE, Interdigital, FirstNet |
| R3-252526 |
(BL CR to 38.401) Support of Multi-hop relay |
LG Electronics Inc., ZTE, Nokia, Nokia Shanghai Bell, Ericsson, FirstNet, Huawei |
| R3-252528 |
(BL CR to 38.473) Support of Multi-hop relay |
Huawei, LG Electronics, Nokia, Nokia Shanghai Bell, NEC, CATT, Ericsson, Samsung, ZTE, Interdigital, FirstNet |
| 22.2 |
Support multi-hop Layer-2 UE-to-Network relay |
|
| R3-251646 |
(TP for TS 38.401 and 38.473) Support of Multi-hop relay |
LG Electronics, FirstNet |
| R3-251647 |
Discussion on service continuity in Multi-hop relay |
LG Electronics, FirstNet |
| R3-251690 |
(TP to BLCR for TS38.423 on multi-hop relay) Discussion on multi-hop relay |
NEC |
| R3-251700 |
Discussion on support of multi-hop SL relay |
ZTE Corporation |
| R3-251701 |
Discussion on service continuity for multi-hop SL relay |
ZTE Corporation |
| R3-251739 |
Discussion on the support of multi-hop Layer-2 UE-to-Network relay |
Nokia, Nokia Shanghai Bell |
| R3-251740 |
(TP for TS 38.470) Support of Layer-2 multi-hop UE-to-Network relay |
Nokia, Nokia Shanghai Bell |
| R3-251783 |
Discussion on multi-hop Layer-2 UE-to-Network relay |
CATT |
| R3-251815 |
Discussion on multi-hop for SL relay |
Samsung |
| R3-251859 |
(TP for SL Relay 38.473) Support onMulti-hop Layer-2 UE-to-Network relay |
CATT |
| R3-251930 |
(TP for SON BLCR for 38.401) SLrelay control plane |
Huawei |
| R3-251931 |
(TP for SON BLCR for 38.401) SLrelay service continuity |
Huawei |
| R3-251961 |
Authorization of Intermediate Relay UEs in RRC_INACTIVE |
Ericsson |
| R3-251962 |
QoS handling for Multi-hop Relay |
Ericsson |
| R3-252295 |
Summary on NR Sidelink Multi-hop Relay |
LG Electronics |
| R3-252344 |
(TP for TS 38.473) Support of multi-hop SL relay |
LG Electronics Inc., FirstNet, Samsung, Ericsson, ZTE Corporation, Nokia, Nokia Shanghai Bell |
| R3-252345 |
(TP for TS 38.401) Support of multi-hop SL relay |
Huawei, LGE, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-252346 |
(TP for TS 38.470) Support of multi-hop SL relay |
ZTE Corporation, Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell |
| R3-252527 |
(BL CR to 38.470) Support of multi-hop SL relay |
ZTE |
| 31.1 |
Corrections |
|
| R3-251591 |
Correction on UE Radio Capability Retrieval |
ZTE Corporation, CMCC, Nokia, Huawei, Ericsson |
| R3-251607 |
Correction on UE Radio Capability Retrieval |
Huawei, Ericsson, Nokia, ZTE, CATT, CMCC |
| R3-252018 |
Correction of the interaction with other procedures related to the User Plane Failure |
Ericsson |
| R3-252071 |
Update of Broadcast MCCH Information for MBS packets discard and multiple cell ID case |
Nokia |
| R3-252072 |
Update of Broadcast MCCH Information for MBS packets discard and multiple cell ID case |
Nokia |
| R3-252111 |
Correction of PEI and emergency PDU session |
Huawei, Qualcomm |
| R3-252278 |
Correction on UE Radio Capability Retrieval |
ZTE Corporation, CMCC, Nokia, Huawei, Ericsson, CATT |
| R3-252279 |
Correction on UE Radio Capability Retrieval |
Huawei, Ericsson, Nokia, ZTE, CATT, CMCC |
| R3-252281 |
Correction of the interaction with other procedures related to the User Plane Failure |
Ericsson, Nokia |
| R3-252323 |
Correction of PEI and emergency PDU session |
Huawei, Qualcomm, Ericsson, ZTE Corporation |
| R3-252383 |
Correction of PEI and emergency PDU session |
Huawei, Qualcomm, Ericsson, China Telecom, Nokia |
| R3-252384 |
Correction of PEI and emergency PDU session |
Huawei, Qualcomm, Ericsson, China Telecom, Nokia |
| R3-252425 |
Correction of the interaction with other procedures related to the User Plane Failure |
Ericsson, Nokia, Huawei |
| 31.2 |
Enhancements |
|
| R3-251807 |
Enhancement of LTE to 5GS mobility restriction [Enhanced Mobility] |
Huawei, NTT DOCOMO INC., Nokia |
| R3-251817 |
X2 TNL address exchange |
Vodafone, Ericsson, Huawei |
| R3-251818 |
Xn TNL address exchange |
Vodafone, Ericsson, Huawei |
| R3-251819 |
X2 TNL address exchange |
Vodafone, Ericsson, Huawei |
| R3-251822 |
Xn TNL address exchange |
Vodafone, Ericsson, Huawei |
| R3-251858 |
Outcome of Email Discussion Between Interested Companies on X2/Xn Exchange of Signaling TNL Addresses for Signaling Transport Establishment |
VODAFONE Group Plc |
| R3-252032 |
Discussion on E-CID new cell ID indication |
Ericsson |
| R3-252033 |
E-CID measurement enhancement [E-CID-enh1] |
Ericsson, NTT Docomo, Nokia, Polaris Wireless, ZTE, CATT, Huawei, Samsung |
| R3-252043 |
E-CID measurement enhancement [E-CID-enh1] |
Ericsson, NTT Docomo, Nokia, Polaris Wireless, ZTE, CATT, Huawei, Samsung |
| R3-252045 |
Indication of new cell ID for E-CID positioning [E-CID-enh2] |
Ericsson, CATT, ZTE, Polaris Wireless, NTT Docomo, Xiaomi |
| R3-252046 |
Enhancements for Data Collection Reporting |
Ericsson, Jio Platforms (JPL), InterDigital, FiberCop, BT |
| R3-252087 |
Enhancement of NR to LTE mobility restriction [Enhanced Mobility] |
Nokia, NTT DOCOMO, INC, Huawei |
| R3-252144 |
Enhancement of NR to LTE mobility restriction |
NTT DOCOMO INC., Nokia, Huawei, Vodafone, CATT, LG, NEC, Fujitsu |
| R3-252145 |
Enhancement of NR to LTE mobility restriction [Enhanced Mobility] |
NTTDOCOMO, INC., Nokia, Huawei, Vodafone, CATT, LG Electronics |
| R3-252202 |
Further consideration on X2Xn sigTNL establishment |
ZTE Corporation |
| R3-252203 |
X2 TNL address exchange |
ZTE Corporation |
| R3-252282 |
CB:#12_TNLAddress |
Vodafone |
| R3-252283 |
E-CID measurement enhancement [ECID_enh1] |
Ericsson, NTT Docomo, Nokia, Polaris Wireless, ZTE, CATT, Huawei, Samsung, China Telecom |
| R3-252284 |
E-CID measurement enhancement [ECID_enh1] |
Ericsson, NTT Docomo, Nokia, Polaris Wireless, ZTE, CATT, Huawei, Samsung, China Telecom |
| R3-252410 |
X2 TNL address exchange |
Vodafone, Ericsson, Huawei |
| R3-252411 |
Xn TNL address exchange |
Vodafone, Ericsson, Huawei |
| R3-252429 |
X2 TNL address exchange |
Vodafone, Ericsson, Huawei, Nokia, ZTE Corporation |
| R3-252460 |
Xn TNL address exchange |
Vodafone, Ericsson, Huawei, ZTE Corporation, Nokia, Jio Platforms |
| 32 |
Any other business |
|
| R3-252280 |
(Cancelled allocation) |
MCC |